HN user

heax

41 karma
Posts0
Comments29
View on HN
No posts found.

That it can break my back button is also what i took away from this before closing the tab and reopeing hackernews.

If you want the cloud to be a powerful tool you will use their higher level services. These are incompatible and cannot be reasonably abstracted away.

The simple services like files which you could reasonably abstract away in your code you can also migrate when needed.

If you don't want lock in you might be better of with a traditional hosting provider. The cloud is only really useful if you go in with a mindset to embrace what it offers.

If you don't see that the feature would fit your vision of the codebase then just tell them that.

If you think it is a useful feature tell him that you currently don't have time to implement it yourself but a PR is welcome.

Often people only want that there issue is tracked, so to avoid conflict and just do nothing just tell them that it goes into the backlog of future features to be considered ;)

Hmmm, great idea that way cloud providers can extract insane amounts of money from unsuspecting organizations. Let's call it function as a service :)

Code vs. No-code 4 years ago

Wake me up when they develop their No-/Low-code tool in their tool itself. Up to that point it is not better than code itself :)

I know it exists and it is used here everywhere. But those from the article are just using some latex paint, creating road hazards in their self righteous cause.

For cyclists and motorcycles they create additional road hazards by adding paint that gets as slippery as ice when wet. Thanks for nothing.

That is how I understood it also.

The new part of their discovery is that visiting a malicious website can run the attack on servers in the private network via a JavaScript application and websockets.

That means even applications which are not exposed to the internet can be attacked.

I think the simple truth is we simply eat too much.

Possible the worldwide most known modern food product is the Big Mac. Named Big Mac, not Best Mac, think about it. And it doesn't stop there, large pizzas, pizzas with a lot on top, XXL Schnitzels, All you can eat Chinese.

A lot people make quantity a priority over quality, guess what happens :)

I think they mainly employ a JavaScript perspective where a frameworks lifetime is measured in minutes.

Sure many classical backend frameworks use a central database technology which limits their scalability, but the mature frameworks with sufficient backing behind them still do the job and save a ton of time. With those you will end up with a maintainable application on the long term. Think of django, heck even JavaEE if done right.

Most of you are not Google ;)

It allows you to deploy for a few more days. That fixes the "i can not deploy problem" if my customer needs a urgent fix.

Sure you will be as much in violation of GPL as without that (even if you don't deploy you will violate the GPL), but that is another problem which needs to be addressed.

It is not nice, but aside from hobbyists everyone who seriously develops software caches all dependencies in a own repository like nexus etc.

It's similar to backups, if you don't have one your data must be worthless.

It does not matter what you think how good the M1 is, what the author states is the opinion of the potential buyer of a mac out there. I do not see it as so much superior as he does, but the prices will crater because most think it is.