Atom was archived today • Hacker News Board

Re: Atom was archived today

#611

Post by drschwabe » Thu, Dec 22, 2022, 5:22 AM UTC

pizza234 wrote: post #601

drschwabe wrote: post #524

Earlier quoted context omitted.

> You can't get any simpler than JSON. Actually a plain text file containing a JavaScript object is simpler and prettier than JSON. Not universal across languages though I suppose.

JSON, as used in VSC, can be defined as "plain text file containing an object", as configuration files have a hash map as root-level object. AFAIK the difference between JSON (as used in VSC) and a Javascript object are minimal (no quoting for keys, possibly minor other differences) and using a JS object should have significant advantages in order to replace a de-facto standard.

`Template literals ie- multiline strings without needing escape or newline characters is a signficant advantage of JS object over JSON`

some will argue that scripting would thus be possible if the config was simply JS but that is a rabbit hole both on the debate itself and then the potential compexlity of config; there are trade-offs for/against but not a settled matter IMO as there are major projects like neovim that support full fledged config scripting (in the case of neovim they allow use of Lua)

Re: Atom was archived today

#612

Post by nocman » Thu, Dec 22, 2022, 3:55 PM UTC

vips7L wrote: post #607

nocman wrote: post #580

Earlier quoted context omitted.

Yeah, I wasn't suggesting the JVM was bad (on the contrary, I think it is quite good). I was just putting Java in the "crappy language" camp. The best use of Java is implementing Clojure. Of that (Clojure) I am a fan.

I’d rather write Java than be in parentheses hell any day of the week.

There was a time when I had an equal revulsion toward languages with a Lisp-like syntax. However, dissatisfaction with the limitations of most other programming languages, and the influence of a bunch of very smart and effective developers was enough to convince me to give them another look (and try to be open minded about it).

As countless others have said before me, the parens really do cease to be an issue over time (and not really very long of a time either). The power and flexibility gained by writing code in Lisp/Scheme/Clojure or other Lisp dialects really is worth the effort, in my opinion. I'm not saying there are no bumps in the road - there definitely are. However, I have zero regrets about taking the time to learn those languages. Even if I never write another line of code in any of them again, it will still have been worth the effort.

Re: Atom was archived today

#613

Post by ryukoposting » Sat, Dec 24, 2022, 4:02 PM UTC

herbst wrote: post #476

ryukoposting wrote: post #439

Earlier quoted context omitted.

Having used Atom and VS Code on an old laptop in college, VS Code definitely does a better job when you throw it a large file, a first-gen i5, and 4GB of RAM. Likewise, at my first internship, I tried sublime on my work computer, which they had clearly just grabbed from the storage room (Windows 7! In 2018!). Sublime exploded into a million pieces. My point is this: if we're being honest, all Electron-based editors s…

I honestly don't get that use case, I don't open large files in a text editor usually. But I agree that atom sucks in that degree. Maybe slow never was the problem is kinda what my point is. In the end it's just an editor for text.

I like to reverse-engineer web APIs (working on the NBA's stats API right now) and sometimes I have to open/autoformat JSON files with 500k+ lines.

As a firmware engineer, it's also frequently useful to be able to do hexdumps of large binary files in VS Code.

Re: Atom was archived today

#614

Post by lamarcke » Fri, Dec 30, 2022, 5:41 AM UTC

heather45879 wrote: post #471

charrondev wrote: post #433

Earlier quoted context omitted.

As far as I know most configuration can be done through GUI. You have both JSON and GUI views of the preferences. It seems the GUI is automatically generated from the JSON-schema that validates and gives autocomplete to the JSON editor.

VS Code has the power of emacs and an autogenerating UI which maps to the configuration files. To me, that’s the easy way out—make the UI map one-to-one with the data underneath, obviating the burden of considering the UX of each configuration path, and missing out on the benefits of good UX.

It's sad that you were downvoted for this because you are not wrong at all. VS Code GUI config is a mess, and a lot of the settings are not available there. I just got used to messing with the JSON autocomplete.