No one has mentioned Ishmael from Daniel Quinn, where they theorize how modern culture is a cult (has it's own mythology) ingrained to hate or antagonize indigenous cultures, and how even our founding stories (Adam and Eve) are probably adapted from earlier stories from indigenous peoples.
> Once people depend on an application, the cost of its failure has little to do with how much it cost to build. An application that costs $1,000 to build can still cause a $10 million failure.
> As software cost comes down, dependability becomes a differentiator.
Exactly. If he means successful instead, then we can have different definitions of successful. That being said, I don't think most startup founders have the same definition of successful as that meets: dad that wants to be there for their children.
and you could say the same if not better from C#. But those are now becoming niche languages and ecosystems. One for people around microsoft, azure, etc. The other around oracle solutions. There are still pretty interesting projects around it any of them, but they seem to be losing mindshare against other languages.
As I said in the other comment: jsgist, precisely because it's so bare-bones. The data is stored either in a shareable URL parameter, or in a gist if you give it access to you GH account. Everything else is a minimal PWA in a static html file that makes hosting of it super-cheap, so I don't have to worry about greggman pulling it down.
Anyway, the main uses case I see for these playground sites are:
1) small hand-crafted replications of suspected browser CSS bugs or the like, and testing possible workarounds. That often involves sending them to other members in the team (because I use Linux and Android, two colleagues in the team use Windows, and two using Apple products)
2) trying out some idea for how to make a particular component. Which is effectively almost the same as above, since that needs to be tested across browsers.
So I don't need bells and whistles beyond a simple text editor with code folding. That might not apply to everyone else.
Also, the exact same line of thought applies to js benchmarking sites, which is why I use jsbenchit (which is jsgist but for benchmarks). It also seems to be one of the few benchmarking sites without spurious de-opts of JS code, or noise from GCs triggered by the website itself in the middle of a benchmarking run.
I made https://jsmess.com as one of my first vibe code projects and have been incrementally improving it over time when I have leftover tokens...
It's closest to JSFiddle but completely static, hosted on GitHub pages. No server side processing. Projects are private, saved on localstorage and can be shared via encoded URLs.
This has been a really fun way to ramp up with LLM based coding and I learned a ton, and made a tool I actually use quite often.
https://jsbin.com is what I've used since forever, it's fast and easy, used to use JSFiddle before that. I think you used to be able to create "bins" without having to login way back though. Honestly don't find much use for them anymore nowadays, if I want to share any web/web-like I do it via my own servers + domain and send links to people.
If you wrote it on your company's slack space, it is not really private to the company. Everytime I have a "private" conversation in Slack I have the understanding that the information could be shared. Even now there is a share button not for the whole conversation but yes for individual messages
It's potentially open to the public as well, given the right legal action. The Enron email dump revealed secrets that presumably ended several marriages.
Well the Enron dump was in the early 2000s, a lot of that stuff (irrelevant to the litigation) would get sealed these days. There were things like social security #s and bank accounts in there.
> Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we're temporarily pausing new subscriptions and prioritizing compute for current members. Existing subscribed users are not affected.
> We're adding capacity as fast as we can and will reopen new subscription spots in batches.
That might even be a beneficial move, creating (well, actual, not artificial) scarcity works well to draw interest usually. Curious how this one plays out.
