637 karma · joined August 28, 2018
The answer is obvious in both cases; You don't need it and it would be wasteful. If I don't have a huge database with constant read/write calls, If I don't have to try to manage multiple end users submitting content, if I don't need super async real-time snappy UIs to compete with the latest android app fad or session tracking of tens of thousands of users, why would I need laravel?
If nobody rolled their own specifically for what they needed, we would still be writing ASM/APL/Raw hex.
It's on average not any worse than it ever was, but showing us how bad its always been right now serves a useful political goal in division and diversion.
Its not a conspiracy, just stupidity and greed. Outrage generates views and votes, no cartel required.
I'm not gonna go lace up a DC but it's still useful enough that every hardware store around carries rolls of twine right next to the cable spools and zip ties.
You got hacked? You must have configured it wrong because we already told you it was unhackable; Good luck proving it was our fault not yours.
For a humorous example see the origin of "processed cheese".
Work conditions become crap? GOOD. Can't run a business without slaves in shanties tough shit. Free market right?
Product quality goes to shit because you can't afford decent employees in reasonable working conditions? GOOD. The free market in action!
Are you afraid of a free market?
As a question that's dogged us for thousands of years, maybe its time to accept its just a shitty question.
GPS toggle isn't doing much of anything besides application permissions enforcement.
The project you want is "Yocoto", a complete toolchain to build customized embedded OS images.
You would have to build your own analyzer. Grepping the dependencies from the makefile/build data or just parsing the output of dpkg and translating that into yocto build specs is not unreasonable.
I'll bet you it still just vanishes...
Cronjob to an (S)FTP server and an upload script trigger to chown/chmod all incoming files making the whole thing WORM (Write Once Read Many).
Once its submitted the same user account can't alter it. Even if the malware is clever and scans for .netrc and .id_rsa and manages to create its own connection to the backup server it doesn't have access to anything anyway.
Kazakhstan's low-tech approach is just that, low-tech and low-effort. They could have used tons of vectors besides simply saying "install this cert."
A tiny shred of effort would have been to package an "updater" that did the install without explicitly saying that's what it was for. Or better yet: Kazakhstan is committed to a greener more ecologically friendly future! All tax documentation will go paperless! Just use the provided USB Key to access your documents in electronic format!
A small morsel of effort would be to force it on OS vendors through regulation/licensing/threats/money for localized copies. A good deal of effort would hijack CRLs, pinnings, et al while demanding/sneaking the private keys of the CAs.
Public Key Infrastructure is fucking pointless when the infrastructure is precisely what you can't trust.
The drag and drop interface isn't to upload the content to be hosted like a traditional server (what's the point then?) It looks like (without digging through code) it's so they can parse the file-structure and generate the URIs to forward requests.
Nah - that would never happen.
A small service that landed in my lap needed to read(only) a data source that was roughly 10k lines of yaml. No way that was going to be in any way efficient so I asked for suggestions. All the work-a-day devs(I am not) instantly said the same thing without a single real thought about it: Make it a database duh!
Long story slightly less long, Loading up the libraries to interface with a database ate between 2 and 3 times the memory(depending on the DB and lib) that simply loading the entire 10k line yml ate and offered slower performance and required more code.
SQLite was pretty darn close but in the interest of saving developers from themselves vis a vis parameterized queries, or the need to queries all together for that matter, increased the required code for zero benefit.
The service still hums along with a 10k line yaml in memory. "Worse is better" indeed.
Morally repugnant victim blaming by any other name smells just as foul.
Whenever developer sorts get all starry eyed over "DB as an FS", they never consider data exchange between applications vendors and platforms. Their applications always exist alone in a digital vacuum.
Example: Imagine trying to attach an MS Word document stored in this DBFS to an email from a Thunderbird client. What does that look like to the user? What does it look like to the Thunderbird developer?
Abstract and encapsulate so that each application can use their own container format that includes schema and encoding details? Other applications can read this metadata directly from each containerized db object? Cool, we just reinvented the filesystem again.
And we wonder why Microsoft sucks so bad at securing Windows.