lucasarruda

I doubt there is no passkey solution for Linux. Might not have a bundled one (maybe it will be added), but you could use something like KeePassXC, which is open source.

> Depending on the costs, 600,000 euros a month is pretty good even if it doesn't last forever.

What? 600k euro per MONTH is like you can retire forever in one year. That would be 7mm euro. More than like what most people make during their entire life.

But of course they probably made that in revenue, not profit. Still, I bet they are in a pretty good spot to create a new product, company, etc and with a nice cash reserve if they want to retire.

Btw, according to the article they still keep their old customers, so not like the service has being completely shut down. It's just that they can't take new customers, so at some point they should have pretty low revenue, but maybe they still have a fair amount per month like 100~200k with a super reduced team.

Super relevant! And there are tons of companies looking for Rails developers!

I know some people of the community moved to Rust or Node. But the Rails ecosystem is still the most complete out there.

The framework, as the language, is still evolving, getting quicker and integrating will all sorts of other tools (GraphQL, Elastic, etc).

Ruby is much faster in 2.7/3.x as it was in 1.9/2.0 era.

Rails is starting to try dropping node and all the JS package craziness. But still supports all them. So you can pretty much do HTML-over-the-wire, plain jQuery or go full-blown React/GraphQL/API using webpack or similar.

Thanks. Will apply!

I am in the same timezone, except I am not in North America. Is it ok or you can hire only in US/CA?

Thanks for putting that data. It's helping a lot.

It's funny how most companies are not really remote because they only hire in the US (even if you can work PST/EST), so they ignore the rest of the World. But I have been using the 'Anywhere' tag and found a bunch on interesting ones.

My company was expecting some money to come this year – like they always do every year – to keep operating. Except this year money kept getting delayed until it never came. They have literally fired all engineers so the company can keep alive and operate until they find ways to get government or other types of money/assistance.

Not like they did this on purpose, but it was related to this epidemy.

Very sad.

Not to mention, they also "took time to clean up technical debt and improve the overall codebase while doing the upgrade".

That is no easy task, for such a big application.

Intersting. Seems kind of along the lines of Rework.

Of all services mentioned here, this is the one I like the most and the one I think I'll use.

Their pay as you go makes totally sense when you have a static website that will be access sporadically and you don't want to rely in a public infrastructure such as Github.

I also don't want to depend on freemium services, because they could just shut down the free tier any time.

To sum up: no one really knows for sure!

I guess his point is not that Android platform hasn't improved, but the effort itself to develop for it versus developing for iOS platform.

Cost benefit also is probably lot better on the iOS side ($$$ you get to develop an app / time to develop it).

Start based on the project itself.

If it's a personal project and there are no risks involved, it's a change to pick a new, innovative or trendy language, like Go, Elixir, Clojure, Rust, etc.

If it's a personal project, but you want to complete it fast, probably pick whatever you are more comfortable with. Don't try a new environment if you have to deliver in time.

If it's a corporate project and chances you are not alone in that project, pick whatever is more comfortable for the team. Don't try to innovate that much or you have a chance of have a world of not predicted problems with that language/environment.

But if it's a corporate project and you are mostly alone, then you could pick a different language from that world. Some language that you have deeper knowledge that others and maybe you wanted the team to try/adopt. And that's a quite nice opportunity to both showcase you abilities, initiative and the language itself - because companies generally have a hard time adopting new things.