[0] https://en.wikipedia.org/wiki/Good_News_for_People_Who_Love_...
191 karma · joined November 30, 2012
[0] https://en.wikipedia.org/wiki/Good_News_for_People_Who_Love_...
[1] https://github.com/tonaljs/tonal/blob/main/packages/chord/in...
Also note that two of the three authors cited are known for their bare-bones, economical prose styles; not exactly a cross-section of the literary world. (Poe is debatable--he was probably economical for a 19th century romantic, but not in absolute terms.)
That said, I can't say I would turn down a free copyediting job by Cormac McCarthy even if I had to drop all my semicolons in exchange.
Doesn't that make it more one of those situations where the non-documented behavior has become the de facto standard, rather than "wrong" exactly? (I guess it depends on whether that decision is being made consciously by the implementors or just for lack of knowledge of the standards.)
So that's a pretty impressive improvement--3x over 6 years--but I remember Raku being numbers like 4x or 5x slower than Python on benchmarks from the last few years, so by my very sloppy math it's still got to speed up by at least 2x or 3x to go to match Python.
It's also possible that there has been a ton of speedup in the last year-and-a-half since that benchmark, or it's not representative, but that's where I got the idea from.
[1] https://blogs.perl.org/users/sylvain_colinet/2023/01/benchma...
I heard that someone did a talk on why it took so long for the Web 2.0 phenomenon to happen even though the technologies were available for several years before. Can't remember who.
A little known fact is that even streaming updates (e.g. for live chat) were actually not that hard to implement on the front end going back to the original days of XHR, via "long polling" (basically starting a new XHR request that you held open until the next piece of info comes in) though it took until well into the Web 2.0 era for that to be common. The problem was actually on the server side; to cope with long polling, the server would have to keep a long-running thread (and in the case of CGI, a whole process!) for each of those open requests and the servers would get overloaded. Nowadays of course servers have much better hardware, and we have technologies like nginx that can handle huge amounts of connections in one thread.
In principle you could build almost everything in the modern day front page of Facebook or Google results page with the tools we had in 2001, front-end wise, but the servers couldn't handle long polling for the streaming updated needed for things like the Facebook chat. Also the pages are so complex that it would be easy to get yourself tied in knots without modern conveniences like CSS frameworks (or even resets!)
Edit: I think thejohnconway has the answer [1]: the post was written before the Flexbox stuff for vertical centering was widely supported.
There were still less nasty options than 1x1 GIFs available, like "display: table-cell", so it's still very likely a joke.
Incidentally, nowadays we never refer to DHTML because probably over 99.9% of pages use at least some JavaScript and CSS, so it's redundant to even mention them; you just say "front-end development."
> Japan invested on nuclear then nowadays don't want it anymore but now needs energy. One has to see them canceling their planned phase-out, as "in March 2021, only 11 percent of Japanese said they wanted that nuclear energy generation be discontinued immediately. Another 49 percent was asking for a gradual exit from nuclear energy" ( https://en.wikipedia.org/wiki/Nuclear_power_in_Japan#Post-Fu... )
Wow. To have even ~40% of the population not opposing nuclear after a national trauma like Fukushima, shows their sophistication as a people.
I do wonder if spending 40% of your waking hours playing simulators where you dice people up for no good reason, might contribute a little to that attitude. Especially the kids that already aren't being socialized particularly well (abusive parents that barely talk to them, etc.)
Hell, I'd even be alright if it were games that have loads of violence but with a sense of purpose (e.g., the Half-Life series, or many Bethesda games). The truly aimless violence is what kinda worries me.
Or maybe there's stuff like that out there already that we'll be able to share with gretar, in which case, even better!
I think there's a lot of truth to this, but there are also plenty of podcasters who will literally try all the products themselves (or have some staff do so) and if the thing is no good, pick a different sponsor. The biggest shows are often in a position to do this without any real sacrifice, other than the time investment in testing: they have loads of sponsors knocking at their door that are all offering similar (large) amounts of money, so they're free to pick the one they honestly like.
Here, I feel like the gray area is that they're unlikely to have tried the alternatives to the product. So they'll give a ringing endorsement of Squarespace or Mailchimp or Purple mattresses, but all that shows is that it's probably decent stuff, not the actual highest-quality or best-price option for the listener.
Overall, though, I feel like it's practically a miracle that we have an online media industry that is free of the totally maxed-out creepiness of website advertising (tracking across media, profiling down to the individual level, etc.) And it's even making money. Just listen with a healthy skepticism about the ads. I think most people do.
And then as far as "bass player," that's just a proxy for low income; I also picked a hyper-niche genre that even most metal listeners don't enjoy. If he can prove income via sending copies of contracts with music venues or something, more power to him.
For good or bad, this all stuff that could plausibly be used as an accurate source of information about someone's ability to pay and to not be a problem to the other tenants--especially the lying part.
Not saying this is a net positive for society by any means, but just another example of a potentially legitimate use for doing online research about someone.
And I mean this on the scale of years, not just the 6-12 month "just getting the basics" stage of learning to be a dev.
If we still had the position of "front end developer" in the old sense of writing HTML, CSS, and maybe some light JS, that's someone who could dedicate their resources to mastering semantic CSS. Sometimes I wish there was still a job like that, but for whatever historical reasons, at most companies what we have is a combined role called "front end developer" that involves fairly heavy duty development with client side frameworks like React, but also all of the HTML and CSS stuff. And asking these folks to get good at the semantic side of CSS at the same time as learning all the rest, is asking a lot. Maybe worth it, but it's no joke.