Why not split the frontend and the backend apps into separate applications? That would help with the future proofing since if you wanted to switch to another javascript framework, you could do that.
Nice. Thinking about it more, I think I could live without it but I have it with Gmail at the moment. I like the per-address basis though, in Gmail I add the domain alias then when I add an email alias that alias applies to all the domains.
I don't mean this as a stink to Finmark but it's also a motivating factor to move on to something that better fits your needs as you get bigger instead of trying to squeeze everything out of a service designed for helping startups.
The problem is "technically" still there in Windows it's just that Microsoft decided to push things along by creating WSL which essentially puts Linux (with Linux Containers) on Windows.
The Windows solution is the equivalent of Smart Hulk figuring out time travel.
I'm not against it as much as in aww because the device itself is made of A LOT of legos, so not only do you have a lot of legos from building the sorting device but then you have a lot of legos for the sorting device to be useful.
By name it wouldn't but they link to several files where the "offending code" resides, so if they're using examples where someone is downloading a movie then that would prompt for a DMCA.
I am interested to see how long or if Elastic sticks around after this. If people will just move on to another AWS product or if they'll keep using Elasticsearch.
How would "random" bag checks be milder than video surveillance?
- They're typically not going to be watching it 24/7. They'll only look at the tapes if something occurs.
- Random bag checks, like in programming, is not really random. You either have a particular target or type in mind or you apply it to everyone and bag checks are a lot more invasive than video surveillance.