HN user

nhunzaker

20 karma
Posts7
Comments6
View on HN

As a front-end web developer that has used Emacs for several years, I often feel the pull to Atom. It draws very clear, direct inspiration from Emacs.

Spacemacs is an improvement, however I think it the biggest advantage it (and any other modern text editor) has over Emacs is the on-boarding process and general beginner friendliness.

Beyond that, Atom's modes for front-end web development are pretty top notch. We have js2-mode, and web-mode in Emacs, but the overall experience in Atom is often superior. For example, it's extremely easy to quickly install a color-picker, pull open a CSS file, and use a color wheel to make a hex value slightly darker. More, the color-picker UI feels tightly integrated into the editor.

On the surface, this feels trite, however the slow build-up of user friendly developer conveniences adds up.

The general command over the entire environment continues to draw me back to Emacs. Still, I continue to watch for when Atom can achieve this.

"Bespoke software development using Java, Javascript."

I suppose this means from scratch? Seems like a very important criteria for writing applications with few external dependencies.

That also makes me curious about the approval process for selecting JavaScript frameworks at an organization like this. What is the leading factor -- maintainability?

I tend to agree. Even as an author of one of the Fluxes (Fluxii?) mentioned, I still think this is the best approach. All of implementations I've seen simply formalize patterns the author was repeating on multiple projects.

(There's also know obligation to use them, the joy of OSS!)

Seems like they're using window.history.replaceState, which replaces the current history state. This is in contrast to window.history.pushState which adds to the stack.

I can't help but be curious if it's falling back to #hashurls for you (or something else). From my end, they've come up with a clever technique for persisting map state in a sharable way.