HNHacker News
TopNewBestAskShowJobs

oxidant

173 karma · joined February 18, 2024

submissionscomments
oxidant··on Open source 'Eclipse Theia IDE' exits beta to challenge Visual Studio Code
Astronvim[0] is plug and play. Easy to add LSPs (Mason), easy to add syntax highlighting (TreeSitter), and easy to configure (Lua, no JSON).

I can't stand VSCode due to personal preference [1], but I won't fault someone else using it. If configuration is stopping you from using neovim, use Astronvim or another pre built solution.

[0] https://astronvim.com/ [1] my main beef is lack of support for my ingrained Jetbrains shortcuts and the find window being in the sidebar. How anyone can use the search results easily is behind me. I know you can move it, it's just annoying.

oxidant··on A ChatGPT mistake cost us $10k
My guess is that "now()" is the DB function that returns the current timestamp.
oxidant··on X is justifiably slow (2022)
I had a netbook around this time and putting an SSD in it was a HUGE upgrade (similarly the upgrade from 2 to 4GB RAM).

I still have it, and when I put an 32bit version of Debian on it a couple years ago, it was molasses. Somehow I used it for years with no complaints.

oxidant··on Should I use JWTs for authentication tokens?
Not saying you're wrong about the pronunciation, but "jot" is the suggested pronunciation, not the required one [0]. I used "jay double-you tee" for a long time and it doesn't bother me how people pronounce it.

[0] https://datatracker.ietf.org/doc/html/rfc7519#section-1

oxidant··on Avoiding the soft delete anti-pattern
IMO deleted_at, either with null or epoch as the "not deleted" value is nicer than is_deleted because it allows some level of auditing.
oxidant··on Show HN: es6_maps, new Elixir syntax feature via runtime compiler hacking
Agreed. It's just syntax, similar to implicit keywords (mentioned already) and & anonymous functions[0].

Pattern matching a large number of items off a map is verbose. Putting many new keys in a map can be verbose if they're existing variables.

I'd rather have shorter code that was just as readable than many lines that add to cruft.

[0] Reading `&%{foo: &1.bar}` as a new Elixir dev looks like character soup and is arguably more magical.

oxidant··on Fundamentals of Object Storage in Elixir
You can write a using macro to automatically create a behaviour from specs in a module with https://hexdocs.pm/elixir/Module.html#spec_to_callback/2

It's been a minute but I've done it.

The behaviour/implementation setup reminds me of Java, especially when they're exactly the same.

I do recommend only using mox as far down as possible (only around libraries).

Hammox is Mox on steroids, check it out too.

oxidant··on Tailwind CSS marketing and misinformation engine
I guess I don't see how you lose the cascade by using Tailwind. It doesn't lock you out of defining your own classes or hierarchy.

.frontpage h1 or .frontpage .main-heading is going to have more specificity than .text-xl.

oxidant··on Tailwind CSS marketing and misinformation engine
> ...I have to do a sweeping change to those buttons.

Why aren't those buttons encapsulated in reusable components or templates?

What sorts of changes do you need to make where this is an issue?

oxidant··on Tailwind CSS marketing and misinformation engine
I think it's important to add to the article. Like I said, the one bit of CSS you added is nowhere near the functionality of the Tailwind example you were comparing it to. Without an apples to apples comparison showing _how_ Tailwind should've done it, your words have less power.

---

I read your other article and it still feels superficial and missing details. You compare a demo of a commercially available (effectively "closed source") template against a page you built, but don't provide the source for the page you built. Apologies if it's in the article, but I couldn't find it. I did find the simple blog template on the Nue site, but it had considerably less functionality than the Tailwind demo.

It's still not an apples to apples comparison, because you're comparing a site built with Nextjs to whatever you built. Of course static HTML without JavaScript is going to load faster than an SSG site.

I think the ending quote in the second article is completely unrelated to Tailwind and I'm not sure why it was your conclusion.

> The fact is that Tailwind's popularity will eventually fade. CSS-in-JS is trending now, but standards are forever.

Tailwind isn't CSS-in-JS. You don't need a build step to write it. You need a build step for important features like tree shaking and dynamic properties, but it's not CSS-in-JS.

Including that hurts your position because it sounds like you don't understand what you're arguing against.

Lastly, why so much hate against Tailwind? Positioning your framework as "Nue and semantic CSS vs Tailwind" doesn't make me want to try your framework. Show me why your framework is good and let me bring my own solutions to it.

oxidant··on Tailwind CSS marketing and misinformation engine
One thing I would like to see is a re-implementation of the button in your style of CSS to strengthen your position. I'm not siding with either approach, I just think it would make the article better.

Your, "don't make things cleaner"/"make clean things", images show part of the Tailwind classes used to make the black button on one side and the class "primary" on the other. Elsewhere in the article you define "primary" as only setting the text color to white.

I believe the specific example is a strawperson argument - you're asserting that semantic CSS (as you've defined in the article) is better than Tailwind's approach. However, you don't show an alternative.

---

On a personal note, I've never seen custom (S)CSS written in a maintainable way in my ~decade writing it professionally.

Encapsulating styles by colocating them with the markup (Button.jsx and button.css, styled-components, Tailwind, etc) is the most maintainable way.

I think Tailwind works really well because it eliminates collisions at the global level and makes it really easy to see what a piece of markup will look like without having to change contexts.

As a fan of Tailwind's approach, I like to hear the other side.

← PreviousPage 3 of 3