Readit News logoReadit News
hjadal commented on Ask HN: What Are You Working On? (June 2025)    · Posted by u/david927
davidweatherall · 2 months ago
https://inspo.dev - The idea is a chrome extension that let's you iterate ridiculously fast on frontend web components - click one button, select the element like you're using Chrome's inspect dev tools, press generate, and 60 seconds later, AI has given you ~7-10 new variations on how you could style that component, with the code ready to implement.

Struggling to get the generated iterations to be up to a standard I'm happy with at the moment, but improving every day!

hjadal · 2 months ago
I think a animation or video at the top of the homepage would do wonders for understanding what your extension does.
hjadal commented on Wheel Reinventor’s Principles (2024)   tobloef.com/blog/wheel-re... · Posted by u/TobLoef
mrbluecoat · 6 months ago
Missing point: only reinvent the wheel when you control all the wheels

For large, complex systems with multiple developers this approach rarely works.

hjadal · 6 months ago
It is gonna be a very bumpy ride if not all the wheel makers are in agreement.
hjadal commented on Exploring Gleam, a type-safe language on the BEAM   christopher.engineering/e... · Posted by u/crowdhailer
pmontra · a year ago
It looks like a nice language with the {} syntax to tease all the C and Java developers out there. That's more important than it looks to help spreading the language.

The OTP example lets me state one of my few sore points about all the BEAM languages I worked with or looked at: the handle_this / handle_that madness. Search for "type AsyncTaskMessage" in the post to get there.

I don't want to write code like this (I omit the details, ... are ellipsis from mine)

  type AsyncTaskMessage {
    Increment(reply_to: Subject(Int))
    Decrement(reply_to: Subject(Int))
  }

  fn handle_async_task(message ...) {
    case message {
      Increment(client) -> {
        code ...
      }
      Decrement(client) -> {
        code ...
      }
      ...
   }

I want to write code like this

  type AsyncTaskMessage {
    Increment(reply_to: Subject(Int))
    Decrement(reply_to: Subject(Int))
  }

  fn Increment(client) {
    code ...
  }

  fn Decrement(client) {
    code ...
  }
or any variation of that, maybe this OO-ish one (after all this is a stateful object)

  type AsyncTaskMessage {
    fn Increment(reply_to: Subject(Int)) {
      code ...
    }

    fn Decrement(reply_to: Subject(Int)) {
      code ...
    }
  }
Maybe one of the next BEAM languages will handle that automatically for us.

hjadal · a year ago
Could you possibly do this by transpiling to Gleam? Seems like the transformation is possibly simple enough that it could be done without implementing a new language.
hjadal commented on I learned Vulkan and wrote a small game engine with it   edw.is/learning-vulkan/... · Posted by u/eliasdaler
alexvitkov · a year ago
Vulkan has advantages over OpenGL even if you don't care about visual fidelity.

- No global state

- You can select which GPU you want to use at runtime

- OpenGL error handling is terrible

- Validation layers!!

- Cool official artwork

- Fantastic documentation

- You can upload data to the GPU asynchronously from a second thread in a sane way

- Fancy GPU features - Mesh shaders, RTX

hjadal · a year ago
I will say that validation layers alone are worth it. Damn they are nice, so many bugs in my code has been found by them which saved a lot of time.
hjadal commented on Ludic: New framework for Python with seamless Htmx support   github.com/paveldedik/lud... · Posted by u/paveldedik
smallerfish · a year ago
I second this. kotlinx-html is poorly documented and has a couple quirks, but is fantastic. As I've been building one of my current projects, I've also been building a framework based on jooq + kotlinx.html + javalin + htmx + flowbite (+kotlinjs for a few fancy bits, e.g. the charting library). Aside from tailwind, you end up with a fully typed and compiler-checked application end to end, i.e. no magic strings to be seen. I'm exclusively using HX-Retarget, so the backend is in charge of where things land, meaning that the frontend can do things like:

   div {
      onClick(loadItems)
   } 
I don't know whether I'll ever actually get it in good enough shape to release, but I do plan to blog about how some of the tricks I've found it fitting it together. One thing I definitely need to do before anybody looks at it is clean up how routes and targets are managed.

hjadal · a year ago
That sounds like a lovely way to develop, what is your blog? So I can watch for your post.
hjadal commented on Estimating Software Projects: So you messed up. Now what? (2021)   jacobian.org/2021/jun/8/i... · Posted by u/Brajeshwar
em-bee · a year ago
is not compensating overtime even legal anywhere in the EU?
hjadal · a year ago
It is in Denmark, my contract also states that I work 40 hours a week with uncompensated overtime. The only rules creating a cap on my working hours are the EU's, with 48 hours per week on average in a 4 month period.
hjadal commented on JSR: The JavaScript Registry   jsr.io... · Posted by u/slymax
kwhinnery · 2 years ago
We do intend to take a more editorial approach to scopes, and assign scopes to users in a way we think is more intuitive for end users of JSR. We have reserved some obvious scope names already, but in the future, we'd likely entertain requests to reassign ownership of scopes for the benefit of the broader user community (as in the case of a brand owner requesting ownership of their brand name).

So in the case that a user published "@cocacola/foo", previously published versions of "@cocacola/foo" would remain available indefinitely (unless they were found to be malicious), but we would likely be willing to assign ownership of the "@cocacola" scope to a representative from that brand/company if they asked for it and we could verify their identity. The original author of "@cocacola/foo" would need to publish the module going forward under a different scope.

hjadal · 2 years ago
In the example of "@cocacola/foo" would it allow for the "@cocacola/foo" package to be updated with new versions by the new owners? Or would the foo package essentially be archived and read-only from this point on?
hjadal commented on Technological innovations that produced the shale revolution   construction-physics.com/... · Posted by u/bilsbie
georgewsinger · 2 years ago
I live near Texas. I just filled my car's entire tank of gas (1990 Miata) for ~$22.

How are gas prices in Europe these days?

hjadal · 2 years ago
Here in Denmark it would be around $95 to fill your Miata. Assuming it has a 45l tank.
hjadal commented on Show HN: Heynote – A dedicated scratchpad for developers   heynote.com/... · Posted by u/jonatanheyman
jsdalton · 2 years ago
This is just outstanding. It's so exactly what I wish for out of a scratch pad.

My feature request to add to your pile (possibly a lonely one, since maybe it's just unique to how my brain works):

I really want a scratch pad like this to have UX that supports "inverted" order. Meaning, new blocks get added to the top of the page instead of the bottom. The blocks naturally flow in descending order of creation rather than ascending. The scratch pad always opens at the top of the page. Over time, blocks thus end up "decaying" toward the bottom, with the most relevant at the top.

It just fits better with how my brain works.

I also +1 the sentiment given elsewhere in this thread to bias toward ignoring the vast majority of these feature requests and preserve the simplicitly of what you've built. That includes mine!

hjadal · 2 years ago
I agree that this addition would be very helpful as it is already how I take notes in a markdown document.
hjadal commented on ChatGPT is a blurry JPEG of the web   newyorker.com/tech/annals... · Posted by u/ssaddi
msla · 3 years ago
I notice that the extremists never use paywalls, meaning extremism is allowed to spread unchecked.

If respectable newspapers and magazines cared about society, they'd follow suit, and give the extremists some competition.

hjadal · 3 years ago
I think respectable papers would go out of business if they followed suit. They are usually respectable because they dont rely on a outside organisation for funding, but instead rely on creating good journalism people want to pay for.

u/hjadal

KarmaCake day67September 30, 2020
About
github.com/hjaltesorgenfrei
View Original