Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
_sdegutis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
28 ms
·
241.
▲
by
_sdegutis
9y ago
As I learned modern JavaScript this year, coming from Clojure most recently, I'm really digging JS's destructuring, extended object literals, spread arguments, and lambda syntax. It's a pretty dang sweet language to write in
242.
▲
by
_sdegutis
9y ago
If you guys had a home office position for some of the skills I have, I'd definitely have applied.
243.
▲
by
_sdegutis
9y ago
Sorry to hear that. Have you tried less conventional meeting places like local church events or book clubs at your public library?
244.
▲
by
_sdegutis
9y ago
Have you tried going to local public social events? Have you tried avoiding mentioning your job and just say you work in IT? I'm not saying these will work, just brainstorming ideas. If you figure out the public venues where people wit
245.
▲
by
_sdegutis
9y ago
> Every language will have quirks, but Js certainly has a lot more quirks than Clojure. My team saw a huge gain in productivity moving from Js to ClojureScript on the front-end. Were they using ESNext features? Where they using Babel to
246.
▲
by
_sdegutis
9y ago
> Keeping up with the way Js world evolves is absolutely bonkers in my opinion. By the time you finish writing an app, the whole stack becomes outdates as people jump onto new hot thing. I definitely agree which is why I haven't sun
247.
▲
by
_sdegutis
9y ago
> Big businesses can threaten free speech when they accumulate too much power. For Google, that moment has come. This feels like a bit of an exaggeration in this situation, no? I mean, some states have at-will employment where they can j
248.
▲
by
_sdegutis
9y ago
> For starters, it's a much cleaner and simpler language. This means that you have a lot less mental overhead working with it. I haven't seen much code that uses the bad aspects of JS, or at least exposes it in library APIs. Yo
249.
▲
by
_sdegutis
9y ago
Author here. My main reason for moving away from Clojure and ClojureScript, and not towards Haskell or OCaml or even TypeScript (yet!) but rather towards modern JavaScript, is because in general I've been learning to appreciate the Pat
250.
▲
by
_sdegutis
9y ago
One big downside of SPAs the author didn't mention is the chain reaction effect I wrote about last year[1], where if you start to implement one browser-native feature in JS, it breaks other browser-native features, and it begins a chai
251.
▲
by
_sdegutis
9y ago
I feel similarly about ClojureScript. It's a neat proof-of-concept, but I'm not really sure what it adds over regular JavaScript (or at least Babel + Webpack) these days.
252.
▲
by
_sdegutis
9y ago
Author here. This project was born out of a frustration with the difficulties of adding certain features to Emacs as extensions. It's dormant right now, but it works, and if there's interest, it could see a revival of activity.
253.
▲
Show HN: Leviathan, a Fast Clojure IDE for MacOS
(github.com)
5 points
by
_sdegutis
9y ago
|
1 comments
254.
▲
by
_sdegutis
9y ago
With how many libs I've been able to find on NPM, I don't miss the libraries of the JVM really. Most (if not all) of them have been rewritten by now. And the speed and concurrency of the JVM itself is great when you want to scale
255.
▲
by
_sdegutis
9y ago
Not OP, but I've got 5 years experience writing a Clojure web app from scratch. It began as kind of as a knee-jerk reaction to using Rails for a few years. All the reasons you mentioned are reasons we chose Clojure to implement CleanCo
256.
▲
Age of the Polyglot (2014)
(sdegutis.com)
1 points
by
_sdegutis
9y ago
|
0 comments
257.
▲
Quitting the GUI wars (2014)
(sdegutis.com)
1 points
by
_sdegutis
9y ago
|
0 comments