It's on the homepage under "Recent updates".
HN user
Manfred
I'm Manfred, read more about me here: http://manfred.github.io/.
Please don't give your users a nickname like "tanglers", groups come up with their own nicknames. It's not as infuriating as when New Relic started calling everyone "Data Nerd", which is actually offensive to me and weirdly aggressive for a corporate product.
Companies buy cloud services because they want to reduce in-house server management and operations, for them it's a trade-off with hiring the right people. But you are right, when you can find the right people doing it yourself can be a lot cheaper.
Around 2010 I met a friend at a bar in San Francisco and within 10 minutes we were approached by someone with a chocolate bar startup. It may have been vaguely associated with developers or maybe I'm misremembering. We got a free sample and I explained I didn't live in the US and I also wasn't an investor. They left and moved on to the next group of people at the bar.
This has always stuck to me as an example of the pinnacle of collective investment delusion that seems to exist in certain circles. They idea that you can shape the world to your product instead of improving the world with your product. You just have to try hard enough.
DDoS saturates the network, not the service. Even a box doing nothing would still be unreachable.
To prevent abuse, for example to prevent an old owner of domain to have a valid certificate for the domain indefinitely after transfer.
I had the same experience. It's even more confusing when you want to create an API key because they are separated by product, maybe?
Why wouldn’t it be? It’s a mean derivation of their company name.
Maybe publicly invisible, but a personal network and resume have always been important in a career.
Seaweed :)
Even following their own "getting started" tutorials you get stuck at step one trying to find Visual Studio or whatever it's called nowadays.
Fuzzy automated reviews should always run in an interactive loop with a developer on their workstation and contain enough context to quickly assess if they are valid or not.
When developers create a PR, they already feel they are "done", and they have likely already shifted their focus on another task. False positive are horrible at this point, especially when they keep changing with each push of commits.
Especially with small datasets it’s more important to be exact at the expense of a user having to fix a typo.
I have also seen situations where sales opted into Microsoft early on. When they grew in relation to engineering forced the rest of the company to standardize to Microsoft products so they could get better rates and “save money”.
The fight against “left” and “right” is just a narrative to gin up allegiance with certain groups.
The only relevance to the article is that it indicates which parties have sided with the US administration to fight consumer’s digital rights.
It seems more likely that people will buy a digital copy of the book for a few bucks and then run the TTS themselves on devices they already own.
Which is why you put them in the sea or in places with sparse population.
I guess Denmark is going to be out of the question now.
A microservice architecture would probably use a message bus because they would also need to broadcast the result.
I can definitively see use cases for both
Me too, I was just wondering if you have any real world examples of a project with a large payload.
In my experience you want job parameters to be one, maybe two ids. Do you have a real world example where that is not the case?
I would hope the trillions of dollars sloshing around are used to pay people to make the core of the product better.
*Danish
I wouldn't call it confusing because the rules are very regular. Prepositions and articles are lowercase unless they start the sentence, the same rules apply to spelling in titles (eg. book titles).
As an outsider this feels like they treat these kids like cattle.
I use Pop!_OS for my gaming PC and I generally enjoy it. It could do with less punctuation in the name because it makes it harder to search the internet for distro specific information.
It links to annex 3, and you can find everything at https://artificialintelligenceact.eu/
This argument would have a lot more weight if it was published in a peer reviewed journal by a party that does not have a stake in the AI market.
I think they are hinting at the idea that a long running process on a dedicated server should allocate all necessary memory during initialization. That way you never accidentally run out of memory during high loads, a time when you really don't want your service to go down.
You would need so much more physical memory with this approach. For example, you may want to allocate a lot of memory for the browser, but then close the tab. 2 seconds later you want to use it for a compiler. And then you switch to a code editor.
In our case we were working on a Dutch project so we used this; AVG is the GDPR implementation for the Netherlands:
https://ictrecht.shop/en/products/handboek-avg-compliance-in...