Just using fluentd to push the files into an ElasticSearch DB and using Kibana as frontend is one day of work for a kubernetes admin and it works good enough (and way better than grepping logfiles from every of the 3000 pods running in a big cluster)
And if something breaks they put the burden on you for not creating backups. Always keep it in writing that you are supposed to work on something else, otherwise you will get the problem down the line
yeah thats why I said it only has the chance, not that it leads to good code
The only thing that has the chance to prevent unmaintainable garbage code is a plethora of linting rules.
The adapter is still the inconvenience for me, just because the other option is a (tiny) inconvenience for you doesn’t change the fact that the adapter is an inconvenience for me.
The adapter IS the inconvenience.
PgUp and PgDn are also extremely useful when scrolling through logs
The problem currently is that it looks cheap and out of place a lot of the time. I have seen quite a few games that use GenAI to add Assets and more to their game and currently it boiled down to these options:
The first problem can already be solved, but it takes a lot of work to get to the point where everything looks like it fits your game. I don’t think anyone will complain about GenAI when everything fits your game.
But don’t forget: We are talking about MtG here. WOTC sells MtG cards for an insanely high price and the art is something that makes the cards somewhat worth the price. MtG using GenAI would be just wrong.
This has nothing directly to do with The Day Before, but: Backing a Kickstarter is something completely different and that has to come into peoples heads. Preorders are for a mostly finished product that will 100% ship. The devs have enough funding from investors and publishers, the game will be released no matter how little preorders they will get. Crowdfunding however is for an idea in its infancy that might never be finished. Crowdfunding is an investment.
But where is the difference in this case, The Day Before? Well, easy: When you invest in a kickstarter, the company has to use the money you invested to actually develop the game. They can’t buy fancy cars with the money, they need to put it to good use. If the company uses the money for their own personal benefit, they can be sued for that. For preorders thats not the case.
I couldn’t disagree more with you.
It’s pretty obvious that they only published the game in the current state because of the lawsuit. The game is a total scam and they deserve the hate from the people that invested a lot of money when backing. Backing on Kickstarter has something to do with trust. Of course, the project may never be finished and that’s okay. But it’s obvious here, that they just took the money and did not use it for the game.
From one Datacenter? Yes. If you put all datacenters into the sea? Definitely not. And if the Bitcoin scumbags decide that this is a good idea and built huge mining farms underwarer it’s even worse. Datacenters are one of the biggest contributors to energy need already, taking up 1-1.3% of global energy demand. That’s no joke
It lost a lot of the super-good touchscreen PDF functionality when it switched to chromium though, which I am still mad about. I hope at one point MS will return the PDF Viewer from the original edge
The main problem with JavaScript and TypeScript is that there is such a little entrybarrier to it, that way too many people use it without understanding it. The amount of times that we had major issues in production because someone doesn’t understand TypeScript is not countable anymore and our project went live only 4 months ago.
For example, when you use nest.js and want to use a boolean value as a query parameter.
As an example:
@Get('valueOfMyBoolean')
@ApiQuery(
{
name: 'myBoolean',
type: boolean,
}
)
myBooleanFunction(
@Query('myBoolean') myBoolean: boolean
){
if(myBoolean){
return 'myBoolean is true';
}
return 'myBoolean is false';
}
You see this code. You don’t see anything wrong with it. The architect looks at it in code review and doesn’t see anything wrong with it. But then you do a GET https://something.com/valueOfMyBoolean?myBoolean=false and you get “myBoolean is true” and if you do typeOf(myBoolean) you will see that, despite you declaring it twice, myBoolean is not a boolean but a string. But when running the unit-tests, myBoolean is a boolean.
I hate Typescript for promising me that nobody can put cyanide on the list, but in reality it disallows ME from putting cyanide on the list, but everyone else from the outside is still allowed to do so by using the API which is plain JavaScript again
JSON would be perfect if it allowed for comments. But it doesn’t and that alone is enough for me to prefer YAML over JSON. Yes, JSON is understandable without any learning curve, but having a learning curve is not always bad. YAML provides a major benefit that is worth the learning curve and doesn’t have the issues that XML has (which is that there is no way to understand an XML without also having the XSD for it)
I don’t really code in my free time, every merge request for a FOSS project I wanted to do so far was for company projects where a feature was missing or buggy. My GitHub and Gitlab accounts are full of outdated forks we needed for a minor change in the FOSS project which I was not allowed to merge upstream
FOSS user:
Wants to improve the software and sees easy fixes, but isn’t allowed to create a Merge Request because company policy disallows you from writing code for other projects on company time
Shared hosting sounds like you don’t have your data stored privately and doesn’t sound like less work for the company.
Don’t look at the name from a technicians perspective, but from the perspective of a manager of a small startup who wants to reduce the overhead for hosting it’s service as much as possible. Also serverless is not wrong per sé, it’s exactly what you as the customer get.
You could spin it the same way for every other instance. Why do you call GoDaddy “shared hosting”, in the end it’s just a pod on a kubernetes cluster. So why don’t you call it “private kubernetes pod”?
I think that’s the main reason, it’s a good name explaining what you can expect: an environment where you don’t have to worry about servers and don’t need an administrator
no it’s the joke. In o-notation you always use the highest approximation, so o(n!²) does not exist, it’s only o(n!)
Otherwise there would never be o(1) or o(n), because o(1) would imply that the algorithm only has a single line of instructions, same for o(n)