martinsnow

Google is a thing

Essentially what you're saying is Google need to tell their users they will lose a lot if chrome is sold, and Google needs to say a few nice things about trump to get the same treatment.

Doesn't sound gdpr compliant

What's unattractive about how do you do fellow humans?

Could it be that some people are not American and pretty tired of the trump 24/7 news cycle?

Thank you

Did the site get hugged to death?

Is this piece supposed to make me feel bad for SAP and their terrible businessess dealings? Lol. You reap what you sow.

I don't understand your comment. You can just do jwt and whatever flavour of front end you want.

I applaud Firefox for lower memory usage but it constantly shits the bed when resuming a new instance with previous tabs. If a tab crashes the whole thing crashes for me and the dev tools are really behind chrome for front end dev. I would also like if they would support input=type number ffs

You bring up bad memories. I fucking hated my htc touch diamond. It was pretty but man was it slow.

Yeah sales speak for themselves

Filsystem level deduplication is always legal

What about those who like working at IBM?

Shipping a laravel image means shipping an image that does queues and an image that does web serving. There's a ton of complexity in that when you have to start scaling your queues independent of your web services.

Edit:

Okay so i realise typing from my phone doesn't help me get the message through i want.

So laravel apps usually works by having jobs run in a cli process that's its own thing. It's still part of the same codebase as everything else, but when you run it, that's it. You just run a queue worker.

Then you can run your application in web server mode, that's when your controllers and all the other shebang is served. Rest controllers, mvc and the other stuff.

So in a typical configuration you run your application in 2 different services. One for queues and one for web. For queues there's a simple queue worker built in but there's also a more advanced called Laravel Horizon which can scale your queue worker processes on a machine. You can deploy as many of these as you want horizontally.

Then you also control however many web servers you want to deploy.

All of this sounds very easy, but it can be quite the headache to setup and maintain. So i think Laravel cloud is a good choice for small to medium teams who just wants to ship features and not want to bother with infrastructure, until the infrastructure starts to become constly.

Small teams don't want to bother with hosting apps. Shipping features equals money.

Humans have a moral compass taught by society. LLMs could also have one if they chose to digest the vast information they are trained on instead of letting the model author choose how they should act. But that would require the LLM to be sentient and not be a piece of software that just does what its told.

Something went wrong: : {"status":422,"statusText":"unprocessable_entity","errors":[{"message":"can't be blank","code":"EMAIL_BLANK"},{"message":"is invalid","code":"EMAIL_INVALID"},{"message":"You cannot refer yourself","code":"BASE_YOU CANNOT REFER YOURSELF"}]}

Hilarious

What's the difference between recycled air thats been cooled and then blown into your bed and the air from your air conditioner?

We're talking multiple multiple business units spread out multiple disciplines. Funnily enough we can settle on a common backend language and frontend language and even frameworks in my org but apparently on HN everyone wants to be special? I would love to see how many features got shipped a week with that setup.

In that case why can't your python engineers learn typescript? There's no performance benefits and a much larger library of tools to choose from.

Much more accessible to frontend engineers so you can detach what would be backend problems to your frontend engineers. Often many microservices will be available but no cohesive endpoint or gateway will be available. Task your frontend with creating the gateway because they know the access patterns and they know what they need.

It drives clicks! I don't understand why someone would buy a bed chiller. But perhaps the US is a unique market.

You don't have to run docker. Containerd is available.

Modem has always been a pain point since it's an entire SoC that had to be shielded from the rest of the system. Apple producing their own modem is a giant undertaking.

It's not so much about who made what. It's about knowing what versions where used and which CVEs are attached.

At my employer we generate sboms for all libraries we use. Why would we pay for them?

Who signed off on this crap?

This is a lot isn't it?

Web development isn't your thing either i see ;)