Hacker News: isleyaardvark

New comment by isleyaardvark in "Apple sues OpenAI, accuses ex-employees of stealing trade secrets"

isleyaardvark — Sat, 11 Jul 2026 16:45:52 +0000

There was a thread here not too long ago about employees getting fired because they were cheating on their expense accounts. C-level execs cheating on pretty trivial amounts. And others brought up star athletes getting paid millions, then getting busted placing thousands of dollars on insider bets. There's a lot of irrationality in these decisions.

New comment by isleyaardvark in "The glass backbone: Why the Army's logistics will break in the next war"

isleyaardvark — Thu, 09 Jul 2026 14:56:36 +0000

It's to distract from the Epstein files.

New comment by isleyaardvark in "Apple to increase spend with Broadcom to produce billions more U.S. chips"

isleyaardvark — Wed, 08 Jul 2026 17:35:25 +0000

> means they can be removed just as easily.

Some of them were removed. And then put back. Then increased, then decreased, or otherwise changed depending on what Trump was thinking at 3am while making social media posts

New comment by isleyaardvark in "Beer CSS – Build material design in record time"

isleyaardvark — Sat, 27 Jun 2026 16:27:16 +0000

It looks terrible on desktop too.

New comment by isleyaardvark in "Software is made between commits"

isleyaardvark — Fri, 12 Jun 2026 15:28:39 +0000

That’s what I do, and I find this talk about “throwing away” code history baffling. It’s version control. Git branching is cheap.

I make a ton of backup copies. I rearrange the history to how I want before I share it (git history split is great). I keep my nonsense, others see a readable changeset. (Only downside is the occasional housecleaning of old branches, but after a while their usefulness diminishes.)

New comment by isleyaardvark in "Moving away from Tailwind, and learning to structure my CSS"

isleyaardvark — Sun, 17 May 2026 16:34:42 +0000

Yes, and that’s what it’s used for now due to the ad hoc development of HTML and CSS.

New comment by isleyaardvark in "Moving away from Tailwind, and learning to structure my CSS"

isleyaardvark — Sun, 17 May 2026 12:48:49 +0000

> Tailwind code is mostly write-only and maintained by viewing what the component looks like.

I’d add that almost all code is like that, if you mean you only write it once and only look at it again if you need to make a change. And with Tailwind you generally only need to look at the one component, instead of having to go to a separate CSS file to look, and then look through the codebase to see if that code is used anywhere else.

New comment by isleyaardvark in "Moving away from Tailwind, and learning to structure my CSS"

isleyaardvark — Sun, 17 May 2026 12:31:13 +0000

I think I can make what I wrote above a little clearer by putting it this way. When the class property gets really long, that's not a violation of separation of concerns, because you are not really co-mingling content with presentation. HTML is not content but contains content.

New comment by isleyaardvark in "Moving away from Tailwind, and learning to structure my CSS"

isleyaardvark — Sun, 17 May 2026 12:27:39 +0000

This is the misconception that has caused so many problems over the years, problems that the Tailwind approach solves.

There was never any separation of concerns within the HTML code, the class="" property is in the HTML and that is the styling info. Devs took the idea of separation of concerns of content, presentation, and behavior as separation of technologies: HTML, CSS, and JS, which is not the same. So they tended to think, "oh no, with classes I've got presentation code in my content (HTML) and I need to put it all in my CSS." But HTML is not content, it contains content. And all the separation of concerns is done with how the HTML is written.

For example take this code

Bleh!

That has separation of concerns. The content is Bleh!, the content semantics are h2, the styling is all in the class, and the data-index is used only as a hook for javascript. Violating separation of concerns would involve using those properties for multiple concerns. Particularly the h2 class="h2" part. It looks a bit silly at first glance, particularly if you have a bunch of

and

's in the codebase. But that has proper separation of concerns, and I have many times run into cases where I want an

or

, and in those cases, because I have proper separation of concerns, all I have to do is change the actual content layer to whatever is appropriate without worrying about the presentation layer changing because someone put an h2 { font-size: 1.6rem; } in the css.
The only difference between the old-school approach and the Tailwind approach is the API between the HTML file and the CSS. The old-school approach tends toward terrible abstractions because devs are trying to code the presentation for an element while feeling they need to describe the presentation in as few terms as possible, because they think that amount of characters is separation of content. Tailwind takes the approach that the class property is the presentation layer and you can use your words to describe it clearly.
I'd add that what I've seen with the older approach almost always leads to much more co-mingling of concerns (maybe because those devs get so focused on "all style should be in the CSS"). That's when I see things like ul > li { padding: 1rem; }, which is fine until you decide to change it to an ol. Or even .foo > .bar { ... }, which is dependent on the structure of the content.
Yes, Tailwind is ugly as sin but it's effective.

New comment by isleyaardvark in "Swift bricks to be installed on all new buildings in Scotland"

isleyaardvark — Thu, 14 May 2026 18:40:46 +0000

Even during the 70s there were already conservation efforts. The Eastern bluebird almost went extinct in the 70s but a bunch of Americans built birdhouses for them.

New comment by isleyaardvark in "If more than 50% press blue, everyone survives. Red pressers always survive"

isleyaardvark — Sun, 26 Apr 2026 23:40:15 +0000

You fail to see how anyone could choose blue, even though there are plenty of people on the internet and even in the comments here who are stating they would choose blue?

New comment by isleyaardvark in "US and Iran agree to provisional ceasefire"

isleyaardvark — Wed, 08 Apr 2026 09:03:13 +0000

Trump could easily agree to it and consider that “their problem”. (I think Iran realize other countries have a say as well.)

New comment by isleyaardvark in "How Pope Leo is pushing back on divine justification of war"

isleyaardvark — Sun, 05 Apr 2026 12:10:33 +0000

Vance has a book coming out all about his conversion to Catholicism. (It has a photo of a Methodist church on the cover.)

New comment by isleyaardvark in "Why the US Navy won't blast the Iranians and 'open' Strait of Hormuz"

isleyaardvark — Tue, 31 Mar 2026 23:07:54 +0000

Brute forcing things is the kind of thinking that leads to the moron losing the game of chess. And is basically the approach the U.S. took in Vietnam.

New comment by isleyaardvark in "Where things stand with the Department of War"

isleyaardvark — Fri, 06 Mar 2026 16:40:12 +0000

20+ years would mean it started to be commonly used around the Iraq invasion, for context on “Orwellian”.

New comment by isleyaardvark in "America's pensions can't beat Vanguard but they can close a hospital"

isleyaardvark — Tue, 17 Feb 2026 19:06:44 +0000

> Still, few people pursue the option because of a “pervasive” myth that the loans can’t be included in the proceeding

It also says nothing about whether the person actually goes bankrupt, just which debts are discharged, which is one of the key parts of the bankruptcy process. Certain debts are discharged because the person can’t pay them back, which is the point of going into bankruptcy court.

New comment by isleyaardvark in "Officials Claim Drone Incursion Led to Shutdown of El Paso Airport"

isleyaardvark — Thu, 12 Feb 2026 02:38:10 +0000

That has already happened before: https://frontofficesports.com/offshore-sportsbook-voids-bets...

New comment by isleyaardvark in "Roger Ebert Reviews "The Shawshank Redemption" (1999)"

isleyaardvark — Sun, 08 Feb 2026 15:21:46 +0000

I rave about "The Secret Agent" (2025) to everyone. It's a slice of life movie about people living under a dictatorship. It's got a lot of heart.

New comment by isleyaardvark in "CIA to Sunset the World Factbook"

isleyaardvark — Thu, 05 Feb 2026 14:25:57 +0000

Like how they deny visas to fact checkers.

New comment by isleyaardvark in "When will CSS Grid Lanes arrive?"

isleyaardvark — Sun, 01 Feb 2026 15:29:38 +0000

There is a use case for grid lane and pinterest is a good example: random images where a user isn't looking for a particular image but is just browsing. That's also why the example looks bad, is because it prominently includes text, which isn't part of the use case. Scannability is terrible, this layout has a very limited use case. It really is only for browsing random images, not even searching for a specific image and definitely not concerned with text.