I'm repeating a point I made in a sub-thread but please WHY should the onus be on yt-dlp to review their decision on a project that has zero commitment to review their very code?
I get the idea to "battle-test" the rewrite first but (a) how does one even determine a reasonable timeframe for battle-testing that much LOC and (b) each vibe-coded update pushed to the Bun upstream basically resets the battle-testing timer. I guess you could lag behind $LATEST by a given window but that just brings us back to (a).
Why should yt-dlp commit to review their decision in the future about a project that makes no commitment (that I've seen) on reviewing their source code?
I get the idea to "battle-test" the rewrite first but (a) how does one even determine a reasonable timeframe for battle-testing that much LOC and (b) each vibe-coded update pushed to the Bun upstream basically resets the battle-testing timer. I guess you could lag behind $LATEST by a given window but that just brings us back to (a).
Given that part of their announcement is to keep supporting pre-rewrite versions of Bun, it implies to me that they are open to reconsider if the Bun team cleans up their act. I don't think it could get any more reasonable than that.
So? Is this where your corporate paying clients should find out about an issue of this severity?
Not to mention Twitter is not an open platform anymore! (A) I'm an employee in an organization paying for Github. (B) I don't have a Twitter account. I already have a Github account because of (A). Why should (B) stop/delay me from getting official comms about this?
> I can't imagine they'd spam every account with an email address
It's not "spam" if it is relevant to me, such as security incident disclosures.
Also, as tiffanyh pointed out, what's wrong with Github blog or is that exclusively for marketing fluff now? That would've been appropriate enough, without having to spend Sendgrid credits.
Ugh this is the dose of cold water from reality that I didn't want but definitely needed.
More than a decade ago I had a project that used a pretty aggressive input-suggestion widget on the UI. We used a jQuery plugin for it and it was by far the most complicated part of the frontend. In fact, it was the main use-case for jQuery in that project.
Reading the article, I thought it would be pretty much a breeze re-implementing that frontend in a lightweight JS-minimalist version. But of course, unless I ship my machine to the users, not really. Sad state of affairs.
Nonetheless, I'm really impressed with what's included in the HTML spec nowadays! I haven't kept-up with developments in the spec since I read all about XHTML in high school. I ought to take some time every now and then to see what's changed though, again, browser compatibility is a PITA today as it was back in high school.
wellackshually the bloatware explicitly asked for consent. There was a checkbox at the end of the EULA asking you "I also don't agree to not install the ask.com toolbar. You wouldn't do that, would you?". There is a state of that checkbox which would not install the toolbar, because, as you know, it's not part of the software I'm trying to install. That state, however, is left as an exercise for the decompiler. :)
Though I kinda agree that framing it as "consent" feels a bit off even if I myself would say no if only Chrome had the courtesy to ask. What icks me more is a 4GB[1] blob that has no relevance to the primary business of being a web browser; this is basically the IE anti-trust issue all over again. And it's an experimental feature! Under saner policies this thing would be a plugin from "Google Chrome Labs".
[1] I found weights.bin in Ubuntu 22.04 Chrome v147.0.7727.137 but it's "only" 2.7GB. Still, my ick stands.
You know there are software which are so marvelously monumental, they inspire me to improve in my craft. Among them in no particular order
- The Witcher 3 (honorable mention, for all its jank, Skyrim)
- Sublime Text and vim
- Krita and Procreate
- Early Google Chrome
- Redis and Postgres
Seeing "steve-yegge.medium.com" on the HN frontpage averts me by reflex. Like, I'm suddenly inspired to learn more about agriculture. Or contracting, I heard that could be lucrative. Heck, I'd even go full hipster and open a bookshop in this economy.
Steve, you probably don't give a shit about my opinion but I just want to know from which Jamaican zip codes do you source your supply.
The bucket on an NPC's head while you rob them blind is my favorite example of a shining success of the line-of-sight system while simultaneously being a spectacular failure of basic AI.
The other nasty bug involving pixelization that we did manage to fix before shipping, but that I unfortunately didn't save any video of, involved the maid NPC, who was originally programmed by a really brilliant summer intern, but had a few quirks:
A Sim would need to go potty, and walk into the bathroom, pixelate their body, and sit down on the toilet, then proceed to have a nice leisurely bowel movement in their trousers. In the process, the toilet would suddenly become dirty and clogged, which attracted the maid into the bathroom (this was before "privacy" was implemented).
She would then stroll over to toilet, whip out a plunger from "hammerspace" [1], and thrust it into the toilet between the pooping Sim's legs, and proceed to move it up and down vigorously by its wooden handle. The "Unnecessary Censorship" [2] strongly implied that the maid was performing a manual act of digital sex work. That little bug required quite a lot of SimAntics [3] programming to fix!
Speaking of physics, the giant striking you with a hammer and launching your body into orbit.
And of course, can’t forget the classic Skyrim pathfinding jank. The number of enemies that would go aggro only to get stuck on a bush or a slight change in elevation while you stand there at a distance peppering their face with arrows until they die.
Your examples are from 10 or more years earlier that Skyrim's creation engine.
That is to say, the older engines could have been limited by hardware requirements, or maybe decoupling physics from fps is an innovation that appeared between 2004 and 2011. Or maybe they are also jank.
Notably, the source 2 engine (2015) decoupled physics from fps (as I understand).
You answer your own question! Not remotely to the same extent. Quake, for instance, gave a small advantage for jump height [with high FPS]. Skyrim would outright break.
Also, you've listed three generations of the same family; goldsrc, the child of Quake, predates Skyrim/Creation by at least a decade. Of those, Source would be the timely match. Not even close to the same amount of jank. Just... no. You aren't tricking me into writing lists.
I don't really intend to be critical of Skyrim, like many: I love the jank. It's expected. It's a Bethesda game.
Double tinfoil hat mode: an attacker learned of my plan to finally update my personal computer out of 20.04 today and is DDoSing canonical so I can't do that and I remain vulnerable to the backdoors they've found.
Man, this SUCKS big time for me. Just a few months ago, $PARENT_CONGLOMERATE mandated all under its benevolent wing to migrate to GitHub for reasons of synergy and efficiency. So now it's my turn at $DAYJOB to be migrating us from our self-hosted Gitlab instance. I already have a few grievances...
- IT policies around GH accounts make no sense. It's a long story but, in short, you can't use any of your pre-existing GH accounts whether personal or professional (as in, an account I made exclusively for $DAYJOB before The Synergy Mandate) and must create a new one aligned with IT conventions.
- We don't monorepo hence we made extensive use of groups. There is no direct mapping for this concept in GitHub so we have to manually namespace projects.
- And now of course GH's no-nines availability :(
For my team, profit happens to be sensitive to our release dates---a day or two of delay can really make the difference if we'll make the month's projections or not. In another world, I would proactively mirror our profit-essential code but it's not worth the risk making a skunkworks guerilla effort. I'd like to think we can blame The Synergy Mandate in a few postmortems in the near future but of course I did not graduate yesterday, I know that's not gonna happen.
Thoughts and prayers we keep hitting our profit projections and they don't axe our product for underperformance.
(Writing this down, I can really feel how this job has changed since I joined.)
> inconsiderate of 1 in every 10 people in public spaces.
It's high-impact for you but low-impact for humanity in general or even just for businesses with a rat problem.
1 in 10 is exactly the definition of "low impact". I get that it's a ginormous inconvenience to the dozens of you out there---and as a person with his own allergies, albeit not to cats, you have my sympathy---but that doesn't change the fact that 10% falls pretty squarely under the definition of low-impact.
In a city with a population of 8.5 million 10% is easily under nine hundred thousand people, such a low impact indeed ... 'dozens' might be overstating this /s
You're claiming that the single most common allergy suffered by humans is low impact compared to a $2 rat trap which doesn't bother anyone. The cope...
You can just say you like cats. You don't have to invent fallacious reasons for it.
Is there a tenable workflow for the marketing department to use a SSG over Wordpress?
- WYSIWYG editor is table stakes. The lovely folks at marketing once thought I was hacking when I `ps -eaf`-ed in an unresponsive Macbook.
- They "put" images in their post. They don't "upload the image and position it with CSS".
- It's the marketing department so they have to have all sorts of bells and whistles. At the very least tracking, at most some obscure integration plug-in that as an engineer I have no kind words for. Social integrations and "You may also like..." sections also come to mind.
> cheap WP plugins that export the whole site as static to something like FTP or S3, so you can just firewall the actual WP behind an IP restriction and host the actual public-facing site from S3/whatever.
Not that I have extensive WP experience but unless you can name me an actual plugin that has good street cred for being used in the wild wild west, I'm gonna say this is not as easy as you make it sound. For one you just described a very rudimentary data pipeline which someone has to support and maintain even infrequently. Also, speaking from experience, plugins don't always play nice with other plugins. I once tried to export my very basic personal site out of WP to find the footnotes all messed up (I don't know now but back then I handled footnotes with a plugin).
I think that's exactly the point where the article falls flat. There is potentially a big oppurtunity in building a SSG + CMS solution despite the past failed attempts.
Every few years I go looking for something that's not Wordpress that you could hand to a marketing department, but there is no viable alternative (that's not Drupal).
> It's the marketing department so they have to have all sorts of bells and whistles. At the very least tracking, at most some obscure integration plug-in that as an engineer I have no kind words for.
The world would be a better place if you forced the lovely marketing folks to use a SSG and you know it!
I taught several absolutely non-technical people to edit the content of Jekyll websites we maintain together. I made them GitHub accounts, taught them the basics of Markdown, and said that if they break anything I can fix it easily, so they shouldn't worry about it. Sometimes they break things and eventually I fix it. It works great. I can only imagine the horrors I'd have to deal with if there was WYSIWYG!
I get the idea to "battle-test" the rewrite first but (a) how does one even determine a reasonable timeframe for battle-testing that much LOC and (b) each vibe-coded update pushed to the Bun upstream basically resets the battle-testing timer. I guess you could lag behind $LATEST by a given window but that just brings us back to (a).
reply