elnygren

Ooff, this seems a bit sketchy. We recently looked at GA runner alternatives and decided on https://avrea.com. See if you have a better experience with them :)

There is likely some reason why they all look the same and also happen to be some of the best performing companies there are.

Since they have a /pricing page it would seem their business is not to make it easy to self-host but in fact to make people pay for the cloud version instead.

Why are people so hostile towards BSL? Paying/asking money for great products is fine and if the product's source code is in git, the better.

Not everything has to be _free_. The major benefit of OSS for many is that you can read the source code. The major benefit of paid SaaS is that things just work and you pay for that. BSL can be the perfect combination of these.

audience

GitHub is the logical place for an “awesome react” list even if it’s not necessarily intended for that.

Oh my sweet summer children. Feels like the author has perhaps never worked on a complex, big product or with any capable engineering management.

The worst and biggest messes in software engineering that I've seen have been situations where there was not enough engineering management. And those situations were fixed by... introducing proper engineering (and product!) management.

That being said, it is perhaps possible to survive with less engineering management in a situation where everyone is behaving and performing at senior or above level. However, realistically, that is very rarely the case.

Sounds like a government intervention is needed and the monopoly should be broken down for a better functioning market.

However, I guess big tech companies have become part of the superpower games (USA vs. China etc.). Breaking up Google might just mean a Chinese company takes over. Can't trust the other governments to enforce similar market conditions.

So yeah, like you said, conditions of the universe :)

I’m curious, how does this project compare to slonik that is also a fast, lightweight, full featured, using SQL template literals etc ? Is there any reason to consider switching, for example?

Out of curiosity, where do these ratings come from? From the PMs? Or do you have EMs who just listen to the PMs in these things?

I already have a way to unify my messaging across different apps. It's called MacOS and cmd+tab. Sometimes on the road I use something called iOS. Sure it's not the same. But is it that different either?

All messaging apps have their own native features, some have E2E encryption etc. Not sure if there's a common subset that is enjoyable enough to use that it's worth it.

That being said, I do wonder what will be the "Facebook Events" (invite all your friends to an event) equivalent in the future when everyone is in a closed garden chat platform instead of Facebook.

It certainly ain't free or cheap if you are running a real business with real traffic and real customers.

However, still totally worth it, easily. Just saying they have a healthy B2B business model.

How to work with libraries like io-ts, Runtypes and Zod to parse all incoming & outgoing data in your applications type safely.

The point of the switch-case is to mimic pattern matching and TS is smart enough tell you whether you handled all cases.

Would you prefer that it's a if-elseif-else based structure instead? I guess that would work too but I feel like it could be easier to write it in a way where you accidentally forget to handle some case (since your else / last return is a potential catch-all).

I personally don't mind switch-case because I'm so accustomed to it in ReasonML/ReScript already.

Nocode/lowcode is excellent for company internal apps & GUIs. Imagine things like barcode/QRcode scanner app for warehouse that just needs to send an HTTP call somewhere. Stakeholders/business people might be able to complete some smaller apps & views & GUIs themselves an no need to wait for engineering support.

It's likely never going to produce production quality web UIs for sites that have millions of consumer users where everything has to be optimised by hand but that's not really most use cases or the case for NoCode/LowCode.

I've always preferred Docker for setting up databases and database-like services on a development machine because then everything is nicely isolated. i.e no need to worry about random files in /etc/foo, easy to setup many versions per project etc.

This is what I've been using for Postgres:

        docker volume create postgres
        docker run -d \
          -p 127.0.0.1:5432:5432 \
          -v postgres:/var/lib/postgresql/data \
          --name postgres \
          --restart always \
          postgres

I'm not sure I understand why PostgreSQL would be "overkill" for something? It's very easy to set up and operate, almost anyone in the industry either knows it or they should be willing to learn it as it's the de facto standard for almost any modern company using an SQL database.

Also it's very easy to buy PostgreSQL from various DBaaS providers. There's a docker one liner to set it up on any development machine and you need to run it just once.

Sure, SQLite is a little bit easier but it's so much less powerful as a database. Why not just go to Postgres directly and leave SQLite for what it's intended: embedded programming like mobile apps or in-car entertainment systems etc.

However the schema does look like

type schema = { field1: any, field2: any, ... }

AFAIK the column types are not really enforced and you can even leave them out.

https://stackoverflow.com/questions/2489936/sqlite3s-dynamic...

Ugh a dynamically typed SQL database, no thanks. I always find I have to build quite a bit of a "data layer" on top of SQLite for example when using it in mobile apps.

Also you have to build some basic stuff yourself like Enum or JSON support. It's not hard but honestly I would feel much better using PostgreSQL in those situations.

Engineers are quite choosing beggars (https://www.reddit.com/r/ChoosingBeggars/) when it comes to OSS libraries.

Most of the time OSS libraries are completely free and provided as-is without warranties of any kind. Still people act as if they were a customer who has signed an SLA with the maintainers.

It's OSS, fix it yourself. Or pay someone real money to fix it. Or just buy a SaaS version or paid library. Or DIY.

Why would anyone be obliged to work for free for you?

(yes, some businesses have an OSS product, it changes things a little bit but even still it's as-is without any warranties)

As an engineer if you leave a manhole cover open and people fall down, it is your responsibility.

In an OSS project, you can just provide it as-is without any kind of warranty and clearly tell this in the license.

Maybe you are confusing OSS with actual paid work and paid software (services)?

Of course sometimes the business has OSS components that customers expect to have a certain quality but still... nobody is obliged to work for free, especially if the end user is a for-profit corporation.

I suppose skillful AI/ML people like to think that great AI/ML is all about their skills and the models they produce.

Someone else might think that the true value is in the data, while AI/ML skills can be bought for 120$ per hour :)

Perhaps one day we'll have tools that will figure out the right AI model for you given data, but we won't have tools that can as easily come up with the data.

This is why you want stock/equity instead. Everything else is just toilet paper until it becomes stock/equity.

Usually countries have lots of laws and regulations protecting small shareholders, but not really anything to protect people who might become shareholders one day.

I wish companies had easy ways to give out real stock instead of options... it's up to regulators to make this smoother, easier, cheaper.

because they play in the major leagues where most teams have hundreds or thousands of servers, while they have those nine.

Yes, there is some horizontal scaling, but the sheer amount of vertical scaling here is still mind blowing.

I've run more servers in what were basically hobby projects compared to SO.

Quite a weird rant.

We might just regulate how a TLD works so that there is no domain parking industry and problem is then solved. The party who runs the TLD is surely not going to sell them at a loss since they aren't getting those 5k or 100k amounts even today. They just get 10$ or 100$ per yer or whatever.

If someone doesn't use a domain anymore and someone else has a claim on it, then it just gets moved to a new owner.

Example:

In Finland this is how the .fi domain works, you can get yourcompany.fi if you own yourcompany Oy (Ltd) and someone is just hoarding it. There's a process for this. It works.

"tech/SV" in no way missed out on Defi, they own a pretty big part of it.

Check out a16z, sequoia portfolios or check out the founders of the top defi projects...

"Crypto is what comes after Silicon Valley"

yet some of the biggest success stories to come out of crypto are "Silicon Valley" (or close enough in this context) companies such as Coinbase ?

Current title "Brave acquires search engine to offer the first private alternative to Google" seems quite misleading since there are plenty of private alternatives to Google (search engine) already ?

Especially for english speaking programming and news etc. searches, https://duckduckgo.com is really good.

Also, for using type guards to validate incoming data, check out https://github.com/pelotom/runtypes.

Or if brave enough to dive into the deep end of FP, io-ts is nice. https://github.com/gcanti/io-ts

Good points!

Seems like for "6. Optional properties"

One should rather use tagged unions (see: Abstract Data Types, variants) that are usually written like this in TS:

    type Product = 
     | { type: 'digital', id: string, sizeInMb: number }
     | { type: 'physical', id: string, weightInKg: number }

An alternative take to this article would be that this person wasted two days because he was reluctant to ask more questions from the person who filed the bug report.

How often do you actually receive quality bug reports at work? My experience is that external or internal users almost never provide sufficient information and you as a coder are always expected to drill down on what they reported with a barrage of questions.

ie. if you are not doing https://en.wikipedia.org/wiki/Five_whys then you might be doing it wrong and wasting time because of it.

I'm referring to this:

Some developers would have immediately gone back to the person reporting the problem and required more information before investigating. I try and do as much as I can with the information provided.

Which seems like being stubborn and making a mistake because of it.

Couple other parts also seem a bit overdoing it:

Because I investigated if there were other ways of getting to the same problem, not just the reported reproduction steps. Because I took the time to verify if there were other parts of the code that might be affected in similar ways.

These seem like taking a gamble. Maybe something comes up, but is it more probable that this work should be minimised until there is more proof of "other ways of getting to the same problem"? Developer time is expensive, is this really the best way of using it? Would it make sense to just fix the issue at hand and only put in more time if more bug reports come in after the fix or if there is some other indication that this part of the code might be more broken?

I think platform companies, like Apple and Qt, should not be able to impose such a high percentage as gatekeepers.

I don't think Qt really can... Feels like they're charging way too much, there's not much content and Qt itself is not exactly "hot stuff" right now. (Compared to, say, Apple as the % is same)