> Yes [SW rendering], should have clarified in the original post sorry! Hopefully GPU to come soon, still investigating that. I believed they changed the ISA so we have to modify our compiler, and I love compilers, so it should be fun! :)
I'm not saying this product is good or bad, because I have no idea, but this is priced too low for it's claimed value prop, not too high. 25% of a decked out developer Macbook for something that sets the look and feel of an app and forestalls an entire designer hire is an unseriously low price.
I'm not saying the product is unserious; just that developers are generally unserious about pricing.
> 25% of a decked out developer Macbook for something that sets the look and feel of an app and forestalls an entire designer hire is an unseriously low price.
Potential value bounds the price upper end, but alternatives set what the customer will actually pay. There are much more comprehensive tools of similar nature that are offered for free.
The (somewhat) unique value proposition it offers is in how it integrates into Rails, saving an hour of a developer's time — or a couple of minutes of an LLM's time, if the slot machine happens to work in your favour on that particular spin — required to manually do it themselves. That's worth something, but if you go too high it soon becomes more cost effective to just pay someone to put in that hour.
Pricing per seat makes little sense for a component library. It forces every party involved in building an application to acquire a license, not just a designer who might otherwise have been hired once to provide the assets. Seat-based pricing suits tools people daily drive (Figma, Slack), whereas asset libraries are better priced by what you ship with them.
A more natural unit for pricing would be per domain, application, environment, or similar.
That said, I'm aware several UI frameworks have moved toward seat-based licensing recently, so it must be working for them in some sense.
There are a bunch of those for free no ? Rails blocks (paid, about the same price as this Rails UI), Ruby UI (MIT licensed), I think I saw a couple more here.
The repo was created in May 2023, and it seems like the bulk of commits were made in 2024, before vibe coding was really a thing. I think it's pretty harsh to dismiss projects in this manner.
>Upon release, the album received generally positive reviews from critics, with praise for Top's traditionalist approach and vocal authenticity, though some noted its adherence to familiar country frameworks.
Fun fact for the fans of the “Baba Is You” game[1]:
> the naming of the characters Baba and Keke was inspired by the bouba/kiki effect.
Which makes a lot of sense for a game where meaning itself is one of the core gameplay elements. If you didn’t play that title yet and you enjoy puzzle games, try it.
'Baba is you' is one of the greatest puzzle games ever. The sheer amount of levels and variations is just staggering, although I must say that it absolutely does become quite frustrating at the end, and you can see from achievements that very few people actually stick with the game. While 8% have technically "beaten" it on Steam, you can get that achievement quite early. I have given up after about 60 hours with the game, because it simply stopped being fun, but I still recommend this gem to anyone, just don't be a completionist...
EDIT: Just looked up at 'time to beat' that completionist average is 48h and now I feel very stupid... I find that kind of hard to believe, there were some levels I literally spend 2 hours on, and the full game has over 200 levels... (and I would guess at least 10% of those are very hard).
I'm in the later part of the game and I feel really stupid. Some levels are so small I feel like I can understand all possible strategies but none work. Lovely game overall though, highly recommend!
Loosely related, a html Quine[1]. I like how it shows how little is needed and how far one can bend the rules to fit a particular use case.
For my homepage I also don't use a CMS, I write raw HTML or convert markdown documents; my homepage URL is in my profile.
Consider checking profiles of others too, a lot of HN users share their web pages there, they are often minimal and a great source of inspiration; and there are many cool ones in this comment section already.
I dislike how ai is a major selling point of this computer; then again, I understand it’s a buzzword at this point.
Funnily enough, with the name being “HP EliteBoard G1a Next Gen AI PC”, I know I’m supposed to read it as “(next gen) ai”, but I can’t help seeing “next (gen ai)”.
Article about Norway problem in YAML. Draft is ready (link: https://lab174.com/blog/202601-yaml-norway ), beta readers welcome, please let me know if you have any feedback - thanks!
> Syndication can be done fully automatically by the server
At the risk of stating the obvious: this can get tricky, many popular social media platforms restrict automated posting. Policies around automation and/or api usage can change often and may not even be fully public as some might overlap anti spam measures.
Buffer documents a number of workflows and limitations in their FAQs.
E.g. for a non-professional Instagram account, the user gets a notification to manually share a post via the Instagram app.
> you can prepare your post in Buffer, receive a notification on your mobile device when it’s time to post, then tap the notification and copy your post over to the social network to finish posting.
Postiz docs show that users can create an app on Facebook and use that key and it will auto post.
I guess using POSSE for Instagram forces you to either create a personal app on Facebook which is not easy or make your Instagram account a business account.
Havent been able to figure this out for Instagram - also the only social media that is still relevant for me.
(thankfully?) never got into twitter where it seems to be easy.
I think it would be better to require quotation marks around all string values, in order to avoid this kind of problems. (It is not the only problem with YAML, but it is my opinion of how any format with multiple types should require explicitly mentioning if it is a string type, but YAML (and some other formats) doesn't.) (If keys are required to strings, then it can be reasonable to allow keys to be unquoted if the set of characters that unquoted keys can contain is restricted (and disallowing unquoted empty strings as keys).)
It might be that there’s some setting that fixes this or some better library that everyone should be switching to, but YAML has nothing that I want and has been a repeated source of footguns, so I haven’t found it worth looking into. (I am vaguely aware that different tools do configure YAML parsing with different defaults, which is actually worse. It’s another layer of complexity on an already unnecessarily complex base language.)
The 1.1 spec was released about _twenty_ years ago, I explicitly used the word _implemented_ for a reason. As in: Our Yaml lib vendor had begun officially supporting that version more than ten years ago.
1.1 partially fixed it, so that strings (quoted ”no”) did not become Boolean false. 1.2 strengthened it to remove unquoted no from list of tokens which could be interpreted as Boolean false.
> 1.1 partially fixed it, so that strings (quoted ”no”) did not become Boolean false.
Do you have a source? Afaik v1.1 didn’t introduce such a change, v1.0 specified the same behavior for quoted strings, i.e. in v1.0 a quoted “no” would remain a string “no” as well.
Because there's a metric ton of software out there that was built once upon a time and then that bit was never updated. I've seen this issue out in the wild across more industries than I can count.
I’m not here clanking down on Java for lacking Lambda features, the problem is that I did not update my Java environment past the 2014 version, not a problem with Java.
I think this mixes up two separate things. If you're working with Java, it's conceivable that you could probably update with some effort. If you're an aerospace engineer using software that was certified decades ago for an exorbitant amount of money, it's never going to happen. Swap for nearly any industry of your liking, since most of the world runs on legacy software by definition. A very large number of people running into issues like these are not in a position where they could solve the problem even if they wanted to.
That’s about 99% of the argument I am making. The problem is legacy software and bad certification workflows, not the software being used.
If I’m working with Java it’s indeed conceivable that I could update with some effort.
If I’m working with Node it’s conceivable that I could update with some effort.
If I working with YAML is it not conceivable that I could update with some effort?
PHP is stupid because version 3 did not support object oriented programming.
CSS is bad because version 2 did not support grid layouts or flexbox.
Why should I critique on these based on something that they have fixed a long time ago instead of working on updating to the version which contain the fix I am complaining about?
There is a gradient limit where the onus shifts squarely to one side once the spec has changed and a number of libraries have begun supporting the new spec.
> Yes [SW rendering], should have clarified in the original post sorry! Hopefully GPU to come soon, still investigating that. I believed they changed the ISA so we have to modify our compiler, and I love compilers, so it should be fun! :)
source: https://bsky.app/profile/integralpilot.bsky.social/post/3mde...
reply