As others already pointed out, UUIDv7 is a solid choice and if you don't like the default representation, you can encode the underlying byte array with base62 for example, to get short, URL-friendly IDs.
Readit Newscryptos commented on ULID: Universally Unique Lexicographically Sortable Identifier packagemain.tech/p/ulid-i... · Posted by u/der_gopher
I don’t like or trust Sam Altman, but I do find it disappointing that the megacorps like Google have enough capital and access to customers to just copy their products and win. It feels like our society is broken if there isn’t a way for the smaller companies to win.
That is not quite true. Google did much of the research OpenAI used to build ChatGPT. It is just that OpenAI came up with the first popular mainstream AI tool.
Just look what Google does with its Tensor Processing Units ... they are developing AI chips for a decade now!
... and now we have this damn copilot key on our keyboards!
cryptos commented on Why every Rust crate feels like a research paper on abstraction daymare.net/blogs/everbod... · Posted by u/pansa2
This story reminds of Scala. The language as such is also fine, but has (had?) a cultural problem. There functional programming fundamentalists always promoting the purest solution without solid reasoning - as if god had decided that only pure functional programming is your ticket to paradise. In addition, Scala comes also with powerful language features to build abstractions, like traits, generics, and almost arbitrary names for classes, objects, and functions. All that lead to a culture of unreadably "try to be clever" code.
I'm not sure whether the Scala authors paved the way with methods like :\ (fold left) or whether that happened, because the language had the features, but I tend to assume the latter.
It is a great responsiblity of a language designer to think about what others might do with the language later. Regarding language features the rule "when in doubt, leave it out" applies. See Go (although not my favorite language).
So, basically Product Hunt has become a paid ads platform - only that you wouldn't pay Product Hunt but external service providers. I wonder why PH doesn't take the money directly and switch the business model to some kind of advertising auction. Might be more fair and transparent.
cryptos commented on KDE is now my favorite desktop kokada.dev/blog/kde-is-no... · Posted by u/todsacerdoti
I just find it ugly vs Gnome or Mac. Inconsistent padding, font sizes, colors. Admittedly, this was maybe 5 years ago. Has that improved?
These days, I daily drive Niri and love it. I love the workflow of a scrolling WM. I love that I can configure it via a single text file in the standard configuration directory, I love how lightweight it is. It’s just about perfect for me.
I had always the same feeling. KDE looks okay at first, but on a second look it would be somewhat ugly in a subtle way. That never changed for me in KDE, so I stopped looking at KDE some years ago. But maybe it is the time for another look!
cryptos commented on Help us raise $200k to free JavaScript from Oracle deno.com/blog/javascript-... · Posted by u/kaladin-jasnah
The simple solution is to write everything (for the browser) in TypeScript instead and treat JavaScript only as the compilation target noone actually talks about. And compiling to JavaScript might also become a thing of the past with Webassembly. So, I think we shouldn't care about JavaScript as a name.
Was the tool company named after this man?
It's a damn shame that project Valhalla still isn't finished. This would fix so much and open up java for better matrix math support
The first time I heard about Valhalla was 2014 (if I remember correctly), so more than a decade ago! However, I'm very happy how Java is engineered. It is really the exception that a technology is so carefully developed. Java is the technology you want for long-term stability.
> it's verbose and boring to use.
Python code that follows traditional Python paradigms is called "Pythonic".
Java code that follows Java paradigms is called "awful".
To be fully transparent, I've never written Java professionally, only for a couple small hobby projects 10 years ago, plus some while in school, so my opinion isn't worth the pixels you're reading it on, but I look at most Java code with abject horror.
Endless levels of abstraction. The apparent inability to write a simple function and instead creating a "ThingDoer" class with a single function called "doThing". Run-time introspection and reflection EVERYWHERE. Stack traces that are just an endless stack of calls to functions like ".invoke" and ".run".
I've been under the impression that all of that is a by-product of Java's strict type system, but someone please correct me. Why do Java paradigms seem so awful?
One reason for that Java style is that Java was not such a powerful language for a long time. For example lambda expressions were only introduced in Java 8 (2014) and before that developers need to work around this restriction. A common workaround were/are some annotations above of methods and some reflection magic on top. For example a life cycle callback method annotated with @PrePersist is basically the same a registering a _function_. The whole Lombok library is a massive hack to circumvent some inconveniences in Java (and in my opinion no longer needed).