@problematicparrot Welcome to #fosstodon—sounds like you'll fit right in!
(I initially misread "net security" as "not security", which would have been an odder fit!)
@problematicparrot Welcome to #fosstodon—sounds like you'll fit right in!
(I initially misread "net security" as "not security", which would have been an odder fit!)
> Where I live it can also mean Duquesne Light Company
So, if we had a political video game about politics, and it launched an expansion about the Democratic party taking on your power company, we could have a DLC v DLC DLC
New quick blog post about how you can use a simple bash script (really just a CURL command) to quickly organize your github repos.
https://www.codesections.com/blog/cleaning-github-with-a-simple-bash-script/
Just came across this blog post full of fascinating nuggets about what editors, language use, and coding interviews. https://triplebyte.com/blog/editor-report-the-rise-of-visual-studio-code
Among much else, it shows that #vim and #emacs users both out-perform on interviews: vim users by 24% adn emacs users by an amazing 54% (and, at the other end, IDE users seem to under perform)
But which one is your favorite?
WTF is this spam trying to do now? Got several of those to various addresses, and no, there really isn't anything more in that mail.
@jamesvasile I came here to make that joke too. See also https://slatestarcodex.com/2014/06/08/map-territory-distinctions/
@gentoorebel
There isn't a *ton* that's JavaScript specific in my vim setup, which is part of what I like about it.
I use the following vim plugins for javascript-specific functionality:
vim-mucomplete
auto-completion for JavaScript (non-semantic)
vim-better-javascript-completion
vim-jsx
Syntax highlighting for jsx
vim-javascript
(better) syntax highlighting for javascript
ALE
automatic linting with ESlint (installed separately)
@joseph
> what languages do you use?
I do mostly javascript at work (with the normal amount of html/css thrown in) and mostly rust outside of work these days, but also tend to explore other languages (common lisp in the last few days, a bit of python and a bit of C before that). Part of what I like about using an editor instead of an IDE is that it makes it easy to jump to a different project/language else without losing my setup
> I think that it's mainly Eli Zaretskii who is the actual maintainer of the duo.
Yeah, I realized that after my original toot. I was basing my knowledge on the latest episode of Emacs Chat (http://sachachua.com/blog/2015/12/2015-12-10-emacs-chat-john-wiegley-maintaining-emacs-can-help/) but that is significantly out-of-date and I didn't realize that things had changed.
(Related: any tips for more recently updated Emacs podcasts?)
> I wouldn't trust stats from a single silo.
I'm not looking at the StackOverflow question/answer numbers (though I have in the past for other reasons) but in their developer survey. True, they advertise the survey on SO, so there is *some* bias towards site users. But they make at least an attempt to get respondents through other channels as well. They discuss their methodology here: https://insights.stackoverflow.com/survey/2018/#methodology
@DistroJunkie
> Your post makes me wonder what is the marketshare of Vi(m) and other editors/IDEs.
The StackOverflow developer survey is my go-to source for data like this. It shows VSCode in the lead, used by 34.9% of developers. Vim has 25.8%, and Emacs 4.1%.
https://insights.stackoverflow.com/survey/2018/#development-environments-and-tools
(And VSCode's growth is *amazing*. It was at 7.2% in 2016)
> considering that over the last few years new packages have been developed and widely adopted (magit, projectile, dumb-jump, evil, ivy, helm, ...)
Interesting! My (apparently ignorant!) impression was that those were mainstays of the ecosystem that dated back years. From a quick search, it looks like Projectile is from ~2011, which is newer than I would have guessed. And Helm is from 2015, which is *much* newer than I would have thought.
> I currently bounce between Sublime and PhpStorm depending on the project.
Yeah, I've heard really good things about PhpStorm, but I've never tried it since I haven't had occasion to code PHP.
For the languages I code in, web development in the terminal works really well
@mike put differently, vimscript may well be awful to write extensions in (a d it pretty much is) but if there are 1× as many people hacking away at vim plugins, it might still end up being about as extensible as emacs in practice (from a plugin-users point of view, anyway. Of course there's also the mater of your own config, but a. vimrc can go a long way)
> emacs has been around for over 40 years. It's not going anywhere any time soon.
fair enough, guess I deserve that :D
But I'm wondering less about it going somewhere and more about the momentum of the project/plugins.
I mean, I'm *happy* with vim, so if I tried out emacs, it would be for the extensibility. And that extensibility is less valuable if fewer people are making plugins with it (even if the platform doesn't go anywhere)
How would y'all rate the overall health of the #emacs ecosystem? I'm thinking about making the switch, but I'd want to do it right and don't want to invest the time in a platform without a bright future.
StackOverflow reports that emacs fell from 5.2% to 4.1% from 2016 -2018, which seems large in percentage terms. Does it feel like usage is falling off?
And how is John Wiegley as the new maintainer? I know he had big plans about growing the core team, but I never heard how that turned out.
I switched from Zsh to Fish a week or so ago and haven't regretted it yet.
As @Matter said, it's not to hard to get Zsh set up pretty similarly—I'd previously done that, so it wasn't a big change/improvement for me. But no issues or complaints, either.
(The main reason I switched is that it's much easier to script/extend, which I'd like to do more with soon. I haven't done much yet, but just in configuring it I can see the power. It's also way snappier to start, a nice bonus)
Major struggling with using #Rust traits.
I've put the relevant bits of code here;
https://pastebin.com/tqBLiqdZ
I've written a trait that has associated types <T1, T2>, and is implemented for a struct with basic types <usize, i32>.
In another function with the trait boundary Struct<t1, t2> : trait<t1, t2>, I'm trying to use the object to call the functions in the trait.
Rust is unhappywith <t1, t2>, and instead wants where Struct<'_, t1, i32>: STruct<'t1, i32>
Could anyone please explain why?
@cadadr @apetresc @Tutanota @protonmail
Agreed. ProtonMail now has an IMAP bridge for Linux, so I'm seriously thinking about going that route. It'd be hard to give up Mutt!
Jonkman Microblog is a social network, courtesy of SOBAC Microcomputer Services. It runs on GNU social, version 1.2.0-beta5, available under the GNU Affero General Public License.
All Jonkman Microblog content and data are available under the Creative Commons Attribution 3.0 license.