|
LOL yeah everyone just loves an Amiga clone of a 70s screen editor hack atop a teletype line editor for a rather dumb terminal that lacked independent arrow keys it’s totally not just cooler-than-thou hipsterism to use vim instead of a modern editor that follows your platform’s human interface conventions at least emacs users are amenable to modernization
|
|
|
|
|
| # ? Dec 5, 2025 21:16 |
|
it’s the programmer equivalent of the guy with the handlebar mustache who wears vintage threads and carries an underwood portable typewriter into the cafe to do his writing
|
|
|
|
like don’t get me wrong I’m also not one to use GitHub (a Microsoft company) Atom or Microsoft Atom (VSCode) since web pages aren’t apps, they’re for displaying information, but they try to be at least somewhat modern even as they reimplement the world in JavaScript
|
|
|
|
but you making GBS threads on people about their text editor is different because you called them hipsters oh dear dolores call the police
|
|
|
|
"the web is only for documents" - an equal hipster
|
|
|
|
eschaton posted:LOL yeah everyone just loves an Amiga clone of a 70s screen editor hack atop a teletype line editor for a rather dumb terminal that lacked independent arrow keys i use vim because :s and :v are useful and i can't be bothered to learn replacements. also vi is everywhere very good for editing text. totally rear end for writing code and i think you will find that the hipsters have moved on to neovim, atom and vscode
|
|
|
|
Kevin Mitnick P.E. posted:i use vim because :s and :v are useful and i can't be bothered to learn replacements. also vi is everywhere vscode is normie as hell and that’s why it’s the best one out of these
|
|
|
|
gonadic io posted:one of the things I really like about Rust is that without an implicit self/this, it makes you think about (and clearly mark your methods) for if they are stateful, rely on state, mutate state, etc etc. It breaks down in the context of globals/mutexes but it's still v nice to have. Hopefully not to be too dense here, but I got around to trying what you suggested and have a couple of follow up questions. Here's a playgound with most of what I have: https://play.rust-lang.org/?gist=915186065b07ee90e3d84a6d2ce53d0c&version=stable&mode=debug&edition=2015 My main two questions are: How can I pass in and call the static method DateAdjustment::adjust easily (such as in the AdjustForBusinessDays for NaiveDate? I'm guessing it needs to be wrapped in something (Box?) that knows what the passed in object is and where the method would be, but I was hoping to have something more like in my Scala version where there were singleton object instances that made it easy - is there a way to have a static lifetime instance of each DateAdjustment that can just be pulled in and used by whoever?
|
|
|
|
Shinku ABOOKEN posted:vscode is normie as hell and that’s why it’s the best one out of these
|
|
|
|
i like emacs b/c i think it has a legit better UI and philosophy for editing text for whatever than flavor of the month editors its anachronism has ironically made it make better UI decisions. a text-based interface has lots of pros over guis comedyblissoption fucked around with this message at 11:29 on Sep 24, 2018 |
|
|
|
ssergE posted:Hopefully not to be too dense here, but I got around to trying what you suggested and have a couple of follow up questions. Here's a playgound with most of what I have: is it a requirement that somebody outside this file needs to make their own DateAdjustments? If it's not then the enum version is easier all around imo. one way to bypass the lifetime issue in the trait version is to pass around the type in generics: code:
|
|
|
|
Isn't it kind of overkill to add a generic type parameter that you don't really use just to select which function to call anyway? It seems like there should be a better way to do this. I don't know if using a function pointer would be better, though.
mystes fucked around with this message at 13:31 on Sep 24, 2018 |
|
|
|
hoboman did u rewrite teh forum yet
|
|
|
|
mystes posted:Isn't it kind of overkill to add a generic type parameter that you don't really use just to select which function to call anyway? It seems like there should be a better way to do this. I don't know if using a function pointer would be better, though. yep, use the enum. The issue is having it being extensible in which case the function pointers might be okay. using function pointers though ends up being basically the same thing as the trait: https://play.rust-lang.org/?gist=f7fa45e938afcb499a071d72bd546004&version=stable&mode=debug&edition=2015 which makes sense because the trait is wrapping a single function
|
|
|
|
Captain Foo posted:hoboman did u rewrite teh forum yet what happened with hoboman? did he move to belize?
|
|
|
|
mystes posted:Isn't it kind of overkill to add a generic type parameter that you don't really use just to select which function to call anyway? It seems like there should be a better way to do this. I don't know if using a function pointer would be better, though. A normal way would just be creating a function that takes each type as an argument or something, which in my mind seems like a wash in terms of API clarity. Maybe it's better to do separate functions because it's explicit about exactly which types are allowed? In c# you'd use an interface, maybe, and then that would enforce a certain contract while allowing someone to bring their own thingy, but I don't know what you would do in Rust for that.
|
|
|
|
I'm not going to contradict anyone who wants to poo poo on vim because yes, there's always someone overhyping the old beardy editors. vim is Okay assuming that you have a couple of years over which to gradually learn its ins and outs and what it can do for you. (I'm assuming that emacs is kind of the same thing, but even more so due to easier programmability etc.) sometimes it helps me do some lesser Magic but I'd argue it's not worth trying to learn unless you've got a while to learn it, in the midst of doing other important things. if this makes vim sound utterly useless to you, you've got my blessing: continue ignoring vim
|
|
|
|
learning a greybeard text editor is one of the technical investments that will actually be reasonably guaranteed to pay dividends for at least the next few decades emacs is 40 years old and still going, vim is 30 years old, still going, and that was a relatively smooth switchover from vi, which is 40 years old there will be peeps who are writing poo poo in vim when we all die
|
|
|
|
vim and emacs are dumb garbage that provide no benefit to anyone. their obtuse UIs were stupid even when they were established and were abandoned for modern editors like 30 years ago. nobody should still be using Linux text editors.
|
|
|
|
edit.com supremacy
|
|
|
|
Shaggar posted:vim and emacs are dumb garbage that provide no benefit to anyone. their obtuse UIs were stupid even when they were established and were abandoned for modern editors like 30 years ago. nobody should still be using Linux text editors. rip anyone who has to git rebase -i
|
|
|
|
Finster Dexter posted:rip anyone who has to git rebase -i EDITOR=code supremacy
|
|
|
|
Finster Dexter posted:rip anyone who has to git rebase -i shaggar would unironically recommend a different vcs
|
|
|
|
people who struggle with basic text editors have no business touching computers professionally, and probably should be sterilized, just like people who fail to use turning signals when driving a car.
|
|
|
|
CRIP EATIN BREAD posted:people who struggle with basic text editors have no business touching computers professionally, and probably should be sterilized, just like people who fail to use turning signals when driving a car.
|
|
|
|
they're both basic in functionality but terrible in usability. of the two vim is definitely worse. modal editing is the dumbest possible idea which is why its only found on or promoted by linuxes.
|
|
|
|
the market can stay irrational longer than I can stay solvent shaggar can be wrong longer than I can give a poo poo, longer than the sun can burn, longer perhaps than mankind's whole existence
|
|
|
|
what are the benefits of spending years to learn a bad tool like vim?
|
|
|
|
CRIP EATIN BREAD posted:people who struggle with basic text editors have no business touching computers professionally, and probably should be sterilized, just like people who fail to use turning signals when driving a car. basic text editors like emacs, which requires you to write a bunch of lisp scripts to make it usable, and vim, which just sits there beeping at you while you wonder why the letters you are pressing aren't appearing and half of the document just disappeared
|
|
|
|
The_Franz posted:basic text editors like emacs, which requires you to write a bunch of lisp scripts to make it usable, and vim, which just sits there beeping at you while you wonder why the letters you are pressing aren't appearing and half of the document just disappeared that's the exact kind of person who shouldn't be touching computers
|
|
|
|
help i cut my fingers off with this tool because i lacked the basic understanding of how it works, and i spent no effort to learn it. the tool must be bad!
|
|
|
|
CRIP EATIN BREAD posted:help i cut my fingers off with this tool because i lacked the basic understanding of how it works, and i spent no effort to learn it. the tool must be bad! this is me and accurev right now and i'm not sorry
|
|
|
|
"what do you mean you don't want to use the tool that stabs you in the dick every time you use it? you shouldn't be using computers!"
|
|
|
|
i'd tell u shagger if u watned to know
|
|
|
|
unironic editor wars in tyool 2018 not that i didn't help start it but lol
|
|
|
|
CRIP EATIN BREAD posted:help i cut my fingers off with this tool because i lacked the basic understanding of how it works, and i spent no effort to learn it. the tool must be bad! i love deliberately wasting my own time by choosing the tool that's far more difficult to learn and use well because of its insanely bad interface, even though it's not really faster or more powerful than any of the other choices like, vim is fine. if you're good at it and already used to it, it's probably comparable to any other text editor. but there's no reason to go out of your way to learn it in 2018
|
|
|
|
CRIP EATIN BREAD posted:help i cut my fingers off with this tool because i lacked the basic understanding of how it works, and i spent no effort to learn it. the tool must be bad! no, "basic" text editors shouldn't require you to read a manual just to figure out how to move the cursor, make a simple change and save the file nano and edit.com are basic text editors. vim and emacs are not.
|
|
|
|
if you consider that stuff complex, hoo boy, you must be a web dev
|
|
|
|
the only person who might be getting heated is sh*gg*r, but categorical denials that anyone could possibly derive utility from X are his normal mode of disagreement soo---
|
|
|
|
|
| # ? Dec 5, 2025 21:16 |
|
proponents of vim/emacs will claim that learning them properly lets you edit that much faster by learning keyboard shortcuts for everything and that anyone who wants to be good at touching computers should spend time to learn proper tools for it. these people also tend to be very mad about things like tab order in forms in various applications, etc. there also tends to be a strong overlap between these and people who complain about modern computers being slow. and sure, they have a point. if you learn an unintuitive keyboard interface well, you can get very fast at doing whatever it is designed to do. however, very few people actually want to spend a lot of time imprinting shortcuts for a very specific editor (probably with a very specific config too) into muscle memory, not even people who spend most of their work time with a single tool. in user interfaces, flexibility and intuitiveness has turned out to be far more important than how efficient you can get at using the interface if you spend a lot of time training with it.
|
|
|























