Existenceblinks

I gave you an upvote. There are many legitimate reasons not to start with React in new projects. At this point I think we reach the consensus that React's benefit is only it being popular (hiring pool + libs pool). It's slow and bloat relatively compared to the rest.

I love type languages to the point Typscript is unacceptable. But Elixir/Phoenix has so many nice things to to point that an unsound static type is far inferior.

I'm still unsure whether Docker saves companies money or not. Had spent 10 hours+ for each docker network issue at a company. Scripting is cumbersome but it's mostly write-once, easier to dev/debug/deploy etc.

You know js now has modules and better DOM API.

I wonder you have ever tried doing all of this in vanilla js. Of course you will end up with your own tiny lib, but it's definitely not as hard as React.

I think our industry should accept that React sucks in every engineering metric. And then we move on and no one is going to complain about it.

> No react, no reduce, no apollo or graphql. No typescript, etc.

All of these bring 10 benefit but add 12 problems back. It makes developing project slow at start, slow at medium term, and super garbage at long term. If developers get paid $100k+, I think they should be able to write good codes and have a good team instead of using these to save them from mediocrity.

If you have to really do SPA, pick something that's not bloat, not slow, not flaw .. instead of "hiring pool" BS.

Not all websockets are equal. If you've ever tried PhoenixChannel + PubSub .. you will know why. Also LiveView + Presence built on top of that with all niceties. And if you have more than 1 node, these also work in distributed fashion.

> I see people mess with DOM Api in their application, which is not the right way

I found people who's stuck in DOM abstraction like React keeps reinvesting what platform is already capable of. Some abstract is so nasty e.g. forwardRef .. like really? Real Event bubbling is so much better, it visit every damn node you got the ref for free.

Because it's nicer. The mental model of reading the functions using signals is; it's all about initialize|constructor|new function. And then those off-jsx stuff starts to make sense since you won't re-initialize those things. They need to exist somewhere in particular execution model. In Solidjs, it's effects (compiled from jsx where signals are read). I think those who are familiar with static type languages, naturally understand how signals needs to be unwrap/wrap .. like a monoid, not a big deal.

I dig a bit but not found how the percentage is from. Is it F(#LoC, #download, #repo, #active-in-past-x-year) something? What's the calculation here?

Addendum (since quite many upvotes): for the latter, they break a team of 8 (this is already a small team apart from the whole org) into 2 teams each 4 and break a monolith app into 2 microservices. At the time I saw that, the company started to have more and more managers. Guess what, not even making a break-even yet!

Their local development docs is also nice: https://docs.mathesar.org/contributing/local-dev/

I'm jumping into a django/react project right now and found that there's so much hassle from integrating frontend + django + livereload + deployment. This repo is a good example.

I like to work with companies that make a lot of profit on their 5 digit customers where Single machine is enough. But we can make it 3 behind an LB. I absolute hate business whose infra is a bunch of message broker, lambda, queue .. yet make little money.

I'm about 900km+ far from almost ALL of my friends. It's just 1 hour by flying, of course +3 hours for the whole end-to-end transport ceremony. Plus hotel cost if it's more than 1 day. If it's only 1 day it's also not worth the round-trip ticket price.

I'm ok but please set the config docs cap to 1 A4 size. It should cover 80% of application with zero config. 90% with config. 99.8% with plugins.

My theory is the early employees tend to be more competent than ones in the giant phase. The former built a lot of real shit, the latter learn from existing system and probably do ways few things. A lot of Leetcode engineers as well at some points. It's sort of like the process of getting higher education with a bunch of ineffective tests. Those who are optimized for taking tests passed and got in.

I like that these folks don't just brag "moving off of the cloud" but also sharing their tools to the others. This helps a lot of people save time and money. I am thinking .. that's it? What's missing? I'm on DO app platform now, will try to use their VPS instead with this MRSK.

True. I misread it, it's a zip pattern. I thought it was a fancy list comprehension.

This. DO app platform doesn't support mounting their volume either (wait for 3 years now, and probably won't happen forever). I wonder how render.com make it like it's trivial while the others just assume you wanted a block storage .. nope.

I was about to demo my app to someone and quite shock that my app was down. Though, it's super easy to restart with a single fly command.

I had (a couple years ago) some weird websocket throttle or debouncing characteristic. I tried to construct an evidence, but it's quite hassle so I just ignored it.

I think they are too engineering culture. Target is devs, sure, but they could use some product guys.

Probably a good signal for potential O(n^2) when reading the code.

EDIT: Nope. I was wrong. This is not a list comprehension.

Practically insignificant numbers of company will do it. They are racing to bottom to shirk their own future developer pool.

It's okay. It actually produces the smallest wasm binary size AFAIK. I'm just tired of niche languages already. If I were to go niche why not https://grain-lang.org/ ? It's even a wasm-first lang. Zig is also good and produces small wasm binary. That said, I think Rust/Go is fine.

Yeah, right place, right time, knowing right people. I think it's close to impossible to go through from front door cold.

5+ years elixir exp here, about to take python/django job. Why do you feel sad! I just gave up finding elixir jobs for a couple months.

Ask HN: here is my idea, can I build this in a weekend

AI: of course .. here is your bash script (220 lines long)

On their github repo:

> Simple "hello world" at about 65kb, comparable to React

I assume that is minified and compressed. That's quite bloat. I wonder if they try https://github.com/johnthagen/min-sized-rust ?

Also I feel like the BytecodeAlliance too much focus on their cloud runtime use case while seamless wasm + dom interop is where its adoption will skyrocking. I would rather write Rust/Go/Roc/any-sane-typing instead of TS.

Is there any popular commercial apps based on these? Most of projects I have seen using these tech are developers' side projects.