afaik the basis of it is just that sun/netscape developed js together initially, and sun got the trademark, which got passed on to oracle. not really related to the bad name
brian
joined 2 years ago
yeah uuh, that's ecmascript, the official name of the thing people call js. but everyone still knows it as js. oracle doesn't have any ownership of the language spec. this is purely trying to make the name trademark public
11 and the half of 12 I made it through were almost entirely awful, I don't think I have much hope left for excellence
yeah, ofc it should only be a curated set of errors where the consumer can do something about it. unknown errors should just be opaque 500s
middle ground point: start with the clj dialect for the ecosystem you're most familiar with. cljs for js, clj for jvm, etc. then you're learning the new language stuff but don't have to worry about a new ecosystem.
I love clj. in general it takes more of a pragmatic approach to functional programming than others. you get most of the purity for way less effort. same with specs over proper static types. it just ends up being a very enjoyable and productive language
sql as the language executed by the db hasn't changed notably, but I do think there's been significant developments in ORMs. for a lot of developmers sql is now just an intermediate target
more directly, sqlite was originally for tcl which is why they share the semantics.
also I'd argue that sqlite is a bigger contribution than tk, but I suppose in a more roundabout way
more data for spotify, and more lock in
instead of a sharing id in the link that doesn't withstand secondary sharing, removing, etc, they now get who sent you the link, whether you opened a link sent to you, how long, etc. also encourages people to actually use the follow feature
instead of your friends sending you spotify links in whatever platform that you can go look up on a different music service, you have to use spotify to get their messages
I just miss the friend activity panel. that's as far as the social features should go. maybe it'll get some love with this
did you read it? apple throttled device performance. google is throttling charging speed and battery capacity for safety reasons. there are literally phones melting. also, battery capacity is something people assume will go down over time. also they're giving clear notifications when people are affected.
it's not really the same, and definitely not worse
I'm not sure if I understand why. I like snapshot testing, but I'm not sure what you gain from using this dsl approach instead of a snapshot library and a more typical test framework, but there are some notable downsides:
- you have to write typical tests in a different place from your snapshot tests. some things are more complex than "this value never changes", you might just care about a property holding, it produces the same value for several different inputs, etc. properly capturing a big for a regression test is more than a snapshot
- you lose editor tooling, I can't just send tests to the repl from my editor, I don't have autocomplete, etc
- need edn serializers for all values you care about. seems easy enough to return a host language object without a proper representation
- may just be me but I'm not a fan of the added levels of nesting
steam is one of the few commonly used 32 bit apps left on linux.
I imagine most of it is bc most other things are oss and have been updated/rebuilt already. having to run a 10 year old binary happens way less on linux than it does windows.
a handful of distros have tried to remove 32 but support they've gotten backlash bc they'd lose steam support. linux the kernel won't drop it any time soon, but there's a good chance that if steam drops 32 bit, so will fedora etc