HN user

HungSu

194 karma
Posts3
Comments47
View on HN
Ember.js 7.0 2 months ago

I'm glad to see Ember is still in development. There are a lot of good architectural decisions in there that I miss when I'm in React, and there's a lot that casual React developers could learn from it and other opinionated frameworks. It was sad to see that Ember was held back by obsolete design choices for so long (Vite took years!! And AMD modules are only being deprecated now in this release)

I'm observing recurring patterns in Tailwind-only users: they learn a lot of non-transferable and bad habits, especially when the codebase scales up:

- Engineers never learn to properly use developer tools to debug CSS

- Components get gigantic bloated piles of classes that are not human readable

- Those gigantic piles of classes get logic in them, that often would have been easier to write as a CSS selector. Tailwind developers learn to write a JS ternary operator with a string of classes instead of ever learning how CSS selectors work

- Those ternary operators get too complicated. The engineers write object maps of Tailwind classes, or export consts of strings of Tailwind classes to use later. Those object keys and const names are what the CSS class names could have been if they just used CSS. They literally re-invent CSS classes, but worse.

- Tailwind classes can't be migrated. You can migrate CSS to Sass to CSS modules to Emotion CSS to etc mostly just by copying them over, because all of those are CSS (with some quirks). Tailwind classes are non-transferable

The happiest medium I've found was in an organisation of around 200 UI engineers: scoped CSS so that engineers can work with autonomy without colliding with other engineers, plus Tailwind for quick band-aid fixes.

The author began to realise the truth: that the quality of his writing is very low on average. Then he moved away from that realisation to the thought that Roam or some other kind of automation could somehow save him.

Perhaps what he needs is for the tool to automatically ask him "Is it okay to delete this note from 60 days ago?" That should be long enough for him to lose any attachment to what he wrote and a lot of the time he should say yes, and delete the crap.

I tried this Kanban plugin and ultimately ditched it. I do think it's superior to the other Obsidian plugin, CardBoard (which has some advantages too, namely that it works great with the tasks already in your Obsidian vault) but I ditched Obsidian Kanban because there was no way for me to just view one card. This is a crucial feature for me - while I'm working I do not want to look at the whole board. I want to focus on just the card I'm working on.

Some of my most memorable conversations with my friends in the last couple of years has been talking about games. I've spoken at length about how Witcher 3's writing mirrors real relationships, how Cyberpunk's quests and endings have impact that wouldn't be possible in any other medium, how Return of the Obra Dinn gave a totally new experience that also made me rethink how I learn, and surely many other conversations I've forgotten.

A significant number of people in the HN community either have ADHD or attributes resembling ADHD.

I've personally found browsing websites or even notes in Obsidian to frequently be overwhelming. Switching to an outliner like Logseq really helps ground me and gives my brain room to realign itself on the screen. In particular, being able to click on a single bullet point and make that the app's focus is really the most helpful. If I'm distracted, I have huge struggles remembering what I was looking at before, but with Logseq I can just look at what's focused and I'm good again.

List manipulation features feels much better too. I may type a giant pile of bullets in one place and later realise I want them elsewhere. This is possible in Obsidian, but feels better in Logseq, with lots of keyboard shortcuts and mouse shortcuts available.

As Google Stadia's target user, in my opinion a stronger reason Stadia died is because GeForce Now was a competing and better product.

GeForce Now allowed me to play the games I already own with a more powerful machine than I could buy myself, for just $10/month. Artifacts were noticeable but not enough for me to care. If I bought my own gaming PC later, I would be able to continue playing the game there. GeForce Now offered "Hey, you're playing Cyberpunk at 720p@25fps? Wanna play at 1080p@60fps for $10? And you can leave any time" And I said heck yes.

Stadia would have denied me the ability to continue playing on my own machine while charging me even more money. There are a bunch of stories of people with saved games trapped in Stadia. Google made no attempt to be better than the competition. It's like they're unaware of anything other than themselves.

Perhaps I'm an outlier but PaperWM is one of the things I miss most dearly about Linux. (I'm on Mac/Win for now) I daily drove PaperWM for months and thoroughly enjoyed it. Quirks were noticed but ignorable, in particular I could not get multiple monitors to work as advertised.

Project 4K77 5 years ago

So far this restoration (including money spent on 4K77 and 4K83) has cost TN1 a little over $16,000, but sadly there can be no box office receipts or DVD/Bluray sales to refill our bank accounts when it’s all done.

If you're looking for a cause to donate to, this seems like a good one.