No one likes that either you know.
> Maximalist positions are a thing in our industry. Take a technique, outline its drawbacks, extrapolate you can’t use it under any circumstance, and ban it forever. We are lucky that Rails embraces exactly the opposite…
It is in fact how it was designed to be used, you can read the reasoning here: https://dev.37signals.com/globals-callbacks-and-other-sacril...
> I'm having trouble thinking of a precedent for this - an open source project that has a core API which is effectively a lead generator for their proprietary cloud service. Is this not Vercel’s entire business model? I…
> Walkable, safe and cheap places with good internet have a lot to gain (e.g. Portugal, Thailand) Why do the people living in those cities feel so strongly that this isn't the case[1]? How does the city administration…
Honestly, I do. I love typing M-x with a random word and finding something that does what I wanted to or is pretty close.
It’s the entire premise of Snow Crash.
It already lets you have different settings for the internal en external keyboards by default. I use it just like that - vanilla settings on my MacBook built in and for the external keyboard I switch command and option,…
I don't think the article was saying to choose a market with few customers, of course you want costumers. Rather choose a market with few competitors.
Swift had no horse in that race whatsoever. It was made to interface with Cocoa and it excels at pretty much exclusively that.
I don’t think Reddit being replaced is as much of a given as everyone seems to think. People might simply get tired of the concept altogether. Nobody needs a vote based link aggregator thingy in their lives, and there…
That is the magic of EMacs. If Lem manages to capture that, and improve in other areas like performance - they might make something really special.
If there is data loss it’s an incident, full stop. Your observability layer should be letting you know.
Is your argument that the application gracefully recovering from the scenario will somehow make the dev team accommodated? Hard crashes are not an acceptable substitute for observability, or continuous improvement.
The gustibus is unarguable indeed, but calling it “complex” is definitely one of the takes of all time.
Also Railscasts.
Good catch. It’s been a while since I’ve been thought the ways of old JS so I’m misremembering. It’s all apocryphal anyhow.
Yes, this is it. The MOP approach basically involves using ‘Object.assign’ to instantiate new objects from the metaobject. It is quite straightforward in my opinion, but that is relative I suppose. I don’t know if this…
Not ‘nothing’ has changed. Classes are supposed to be syntactic sugar over constructor functions, but the later could be invoked as well as instantiated with the ‘new’ keyword, whereas the interpreter will error out on…
Also the Nothing Ear (1). I don’t know if they’ve designed their phone too, but it at least follows their design language.
They weren’t criticizing OOP per se. Before the class keyword, JavaScript had much more powerful OOP semantics using metaobjects.
> especially early on when my focus should be testing my product, not optimizing my cloud infrastructure for scale that might never be needed Not to mention vendor lock in, something that really needs to be talked about…
Yeah, it’s the same thing as government issued currency the moment you put it in paper. A corollary is that digital dollars on your banking app is just like crypto.
You can absolutely have both. A little CSS would go a long way here, there is no reason to go full JS SPA to make a page look nice. In fact many times it’s the opposite.
> So things are improving so fast that researchers can't keep up... and therefore nothing will change? Maybe you can ask ChatGPT to summarize the article for you, if you don’t have the time to read it.
No one likes that either you know.
> Maximalist positions are a thing in our industry. Take a technique, outline its drawbacks, extrapolate you can’t use it under any circumstance, and ban it forever. We are lucky that Rails embraces exactly the opposite…
It is in fact how it was designed to be used, you can read the reasoning here: https://dev.37signals.com/globals-callbacks-and-other-sacril...
> I'm having trouble thinking of a precedent for this - an open source project that has a core API which is effectively a lead generator for their proprietary cloud service. Is this not Vercel’s entire business model? I…
> Walkable, safe and cheap places with good internet have a lot to gain (e.g. Portugal, Thailand) Why do the people living in those cities feel so strongly that this isn't the case[1]? How does the city administration…
Honestly, I do. I love typing M-x with a random word and finding something that does what I wanted to or is pretty close.
It’s the entire premise of Snow Crash.
It already lets you have different settings for the internal en external keyboards by default. I use it just like that - vanilla settings on my MacBook built in and for the external keyboard I switch command and option,…
I don't think the article was saying to choose a market with few customers, of course you want costumers. Rather choose a market with few competitors.
Swift had no horse in that race whatsoever. It was made to interface with Cocoa and it excels at pretty much exclusively that.
I don’t think Reddit being replaced is as much of a given as everyone seems to think. People might simply get tired of the concept altogether. Nobody needs a vote based link aggregator thingy in their lives, and there…
That is the magic of EMacs. If Lem manages to capture that, and improve in other areas like performance - they might make something really special.
If there is data loss it’s an incident, full stop. Your observability layer should be letting you know.
Is your argument that the application gracefully recovering from the scenario will somehow make the dev team accommodated? Hard crashes are not an acceptable substitute for observability, or continuous improvement.
The gustibus is unarguable indeed, but calling it “complex” is definitely one of the takes of all time.
Also Railscasts.
Good catch. It’s been a while since I’ve been thought the ways of old JS so I’m misremembering. It’s all apocryphal anyhow.
Yes, this is it. The MOP approach basically involves using ‘Object.assign’ to instantiate new objects from the metaobject. It is quite straightforward in my opinion, but that is relative I suppose. I don’t know if this…
Not ‘nothing’ has changed. Classes are supposed to be syntactic sugar over constructor functions, but the later could be invoked as well as instantiated with the ‘new’ keyword, whereas the interpreter will error out on…
Also the Nothing Ear (1). I don’t know if they’ve designed their phone too, but it at least follows their design language.
They weren’t criticizing OOP per se. Before the class keyword, JavaScript had much more powerful OOP semantics using metaobjects.
> especially early on when my focus should be testing my product, not optimizing my cloud infrastructure for scale that might never be needed Not to mention vendor lock in, something that really needs to be talked about…
Yeah, it’s the same thing as government issued currency the moment you put it in paper. A corollary is that digital dollars on your banking app is just like crypto.
You can absolutely have both. A little CSS would go a long way here, there is no reason to go full JS SPA to make a page look nice. In fact many times it’s the opposite.
> So things are improving so fast that researchers can't keep up... and therefore nothing will change? Maybe you can ask ChatGPT to summarize the article for you, if you don’t have the time to read it.