Blackarea

Well it may not life up to uncle Bob's clean code standards but it does fit the repo's name, doesn't it?

Im on mobile

Captcha fails on archive now? Jeez - free internet is past

A webui halicunated just for you? I think this must be by far the scariest and from my point of view worst idea you could ever come up with, no offense. Why would you ever want your web-experience to be non deterministic. A different ui every time you load? Even longer loading spinners then with mbs of react dependencies today? This is wrong on more levels then I could count

Could make that an AGENT.md and use a dumber model via opencode to slop maxx even harder!

yes! I just don't understand that as well. Up until some time ago claud code's preferred install was a npm i, wasn't it? Please serious answers for why anyone would use a web language for a terminal app

3 source files, nice code, no vibe-coding slob, nice little project... That's rare these days

Bat is nice. Oh dang now i have to try this plugin. I remember trying a couple of similar ones that got me so frustrated that i abandoned the idea of markdown viewers in nvim... Here we go again XD

... Literally ruined

https://youtube.com/clip/UgkxFZA4XXnXzHyNso0OQ28XU60U1-jdR13...

<3 if I don't see 15 new node modules and 3 CVEs by EOB today I'll replace you with a css architect and vibe-coding nft monkey by next week!

Just as the modern Javascript applications. What if - and hear me out on this one - Javascript just is a poor choice for huge complex codebases?

Why they call pipes filter? And if... endif? Not for me

Mass of learning material doesn't equal quality though. The amount of poor react code out there is not to underestimate. I feel like llm generated gleam code was way cleaner (after some agentic loops due to syntactic misunderstanding) than ts/react where it's so biased to produce overly verbose slob.

Grepping "extends" over a new codebase is a quick way to see how fucked you are when joining a new project/team.

I literally couldn't care less. You can call it '1th of April' for all that i care if the actual functionality you offer is clean and fast I'll gladly accept!

btn.finish().with_child(pipe!($read(cnt).to_string()))

You can choose to use it (macros) or not.

Yet both examples use macros.

I might still got ptsd from a job where literally all of the rust codebase was written as macros. Since then I avoid them at all costs.

I find the route, that gleam took, way more elegant with squirrel (sqlx-ish) and lustre (elm-like) being examples of what we could have instead. Avoiding language mixing is so important for proper/clean lsp-support - yet macros are a different language as i see it.

As for the rest of this: i also don't see how it's any different from iced, egui etc. but maybe I didn't take the time to check the details...

Code like a surgeon ... As a UI prototyper

XD yes sure. I'd most definitely put those on the same level. Maybe even favor an UI prototyper if it comes down to the real deal. Who needs an open heart surgery when you can have a magnificent css-hover animation that really seals the deal on some 90%-AI-generated slob that only caters to delusional top-management completely out-of-touch with reality.

Irony off: Let's try it with a bit of humbleness next time, ey?

Oh really a compiled strong and statically typed Language doesn't have a repl? How come?

What? Gleam can compile to js. I don't see the similarity to kotlin being oo and all. Gleams compile time is lightyears ahead of anything on the jvm. I appreciate kotlins nullability constraints but to me it seems the jvm ecosystem is too grown to give kotlin the space it needs. Also heared that java's pattern matching and exhaustive checks have surpassed kotlins? In that case it's just easier to role with java, no?

Profiling tools are something that I miss a bit in gleam - yes, but otherwise I had no problems with OTP bindings. The maturity of the ecosystem is a bit lower of course. But I actually enjoy finding libraries or repos with a few hundred lines. You gotta handroll some things but that's what I am here for. ffi to erlang and js for fullstack apps is as straight forward as it gets, but erlang syntax is indeed a bit crazy. For those interested in gleam but don't want to miss some necessities: https://github.com/gleam-lang/awesome-gleam (the gleam community is super nice btw).

For me some serious elixir adventure is high up in my todo list. But I remain suspicious if I can ever fully enjoy myself with a dynamic language - I think gleam and elixir do cater to different crowds. Gleam is pure minimalism (just pattern matching really), but elixir doesn't seem bloated either.

I am so happy that both languages exist and give alternatives in times of hundreds of node deps for any basic slob webapp.

I really came to love gleam over the last few months. I appreciate elixir getting a type system and remember that this was the big NoGo for me when I explored it a while back. I'd like to give it another chance some time, but I'm worried that it's like typescript - looks typed on the outside but for many libs and packages the types are just a dynamic/any. Is my fear justified? Beam is amazing btw

Do you have any examples. I don't think I would classify more than a handful posts as political myself

It's really a joyful language. Kind off rusty minus the borrow-checker and the mutability. In it's core it's just pattern-matching and functions/closures as first class citizens. The ecosystem is young and you have to search a bit to find the right tools for the job or the gleam way to do things. I tried it because you can use the same language for Front- and Backend it's biggest Frontend lib called "Lustre" is hyped to be the Elm successor. Anyways gleaming away for 2-3 weeks now and it's the best DX that I ever had - no Beam experience upfront btw.

I've never had the need for a gui in sqlite. It's just sqlite3 for me and once I get to a complexity where I'd need a gui I mostly just switch to postgres

I wonder why this was written as these very small paragraphs with only a few lines of content? Apart from the hosting issues due to hackernews it leads to a lot of intros and 'in the next section we will learn...' but the actually useful content is quite little and you have to dig hard for it. I'd personally favor a normal article.

We can just use a crate for that and don't have to have this horrible comment like style that brings its own category of problems. https://docs.rs/indoc/latest/indoc/

Escaping Strings is not an issue. It's guaranteed about UX. Finding a json in your bio is very likely perceived as disconcerting for the user as it implies structured data collection and isn't just the expected plaintext description. The model most likely has a bias of interacting with tools in json or other common text based formats though.

A: So what's your job?

B: I'm senior researcher at openAI working on disclosed frontier models.

A: Wow, that's incredible! Must be so exiting!

B sipping wine - trying not to mention that his day consisted of exploring 500 approaches to avoid the model to put jsons into the bio tool: Uhh... Certainly

Berlin wall of tax? Seriously? Nobody gets shot trying to cross the border here and it's clear that the ones who can afford a decent financial advisory will get around most of the regulations anyways. I don't see how this business economist whining belongs on hn.