spriggan3
How about writing libraries with clean API and encapsulation ? because basically your argument is "Our developers aren't disciplined enough to write clean API, so we need to force it with http calls ...".
Welcome to the Cyberpunk era, where nations are private entities ... I can't wait to play CD Project game by the way.
Give me a break, this campaign is misleading, on purpose, in order to get some money.
They are putting his name everywhere in the campaign like he is involved or something. He is clearly not. That's misleading and can be potentially detrimental to the person's reputation if the campaign ends up being a scam.
Again they might have the right to use his assets, they don't have the right to use his name to get money from people like this. That's completely wrong.
But it shouldn't be up to you or your followers to sort the tweets, I don't understand why Twitter doesn't implement this basic feature. The hell it could be something done in the front-end with no server-side code involved at all.
If Twitter had a way to filter followed people messages by keyword or hashtag It would lead to a healthier environment on that platform. Unfortunately since Twitter basically locked access to its API, writing a fully featured client with that capability isn't even a viable alternative for the terrible UX ...
Definitely fraudulent.
This is already true at the national level and even more true at the supra-national level in EU. I don't want to give more power to corrupt bureaucrates that are completely disconnected from national concerns.
The Eurosceptics don't want a political union for good reasons. It would devolve into a soviet style dictatorship. People that different just can't live under the same government. Europe is not USA. The Eurosceptics are the ones that are grounded in reality here, the other camp is trying to push an utopia that already had horrible consequences.
Why would a student need a special space to feel safe/accepted? Doesn't the university already provide students basic safety?
I never said I supported anything. On the other hand you are quick at forgetting our own moral bankruptcy when it comes to the treatment of minorities in your own country,especially black people. It's easier to point fingers at France than to fix the situation in US. And we don't have the death penalty either. Only barbaric countries allow their states to put its citizens to death. You're not even the pot calling the kettle black, you're worse than that.
And if we keep on using catch-all buzzwords such as "serverless", it makes words void of any real meaning.
The most horrible argument in favor dynamic typing in my opinion. Test suits shouldn't be about checking if a return value is of expected type, that's ridiculous. It's implementing a type checker manually.
There are a lot of things statically typed languages can do to make types painless :
- (global) type inference (Crystal does that)
- co and contravariance, it is not limited to dynamically typed language
- optional parameters
- adhoc type declaration like in C# (ex {x:1,y:"a"} is a type).
- contracts
- pattern matching
- generics
- ect ... etc ...
I just dislike dynamically typed languages. Even interpreted languages should be statically typed IMHO. Again, there are multiple ways to make statically typed language painless when it comes to types.
Obviously we don't as I don't consider the expression "serverless" accurate in describing what is really happening. Call it what it really is : pubsub, calling it "serverless" is misleading marketing.
> You don't need to scale the API Gateway
You still need API Gateway to communicate with the outside world, here is your server, you know exactly what I mean. What you call "serverless" didn't invent autoscaling in PAAS.
It's interesting by the way that you keep using product names "Lambda", "API Gateway" which aren't concepts but Amazon products. That's marketing. It's like calling all social networks "Facebooks". "Serverless" is a marketing device to sell Amazon services, I think people get it by now.
So yes, there is a server indeed. Why call it "serverless" then ? because one part of the stack uses pubsub ? then call that part a worker queue because that's what it is.
It's a bad analogy. As a developer you are supposed to know they are wires somewhere. That's why all this marketing is dangerous. the obfuscation which makes everything sound like "voodoo and black magic".
> The developer doesn't have to deal with servers/infrastructure so for them the system is serverless.
Yes he does, he has to configure and manage the whole thing on Amazon dashboard. Sure he doesn't have to spin upcontainers, but autoscaling doesn't make something "serverless". And again, you need API gateway to communicate with the outside world. So there is still a server fronting the whole thing.