Would you be willing to share what went wrong with your experience of Laravel? I haven't used it for over 5 years, but it was pretty pleasant when I did.
I loved dreamweaver when starting out. Never got on with the WYSIWYG (hence moving on), but its ability to read your CSS file and suggest classes was great. MX was the pinnacle in early 2000s.
More relevant to me though, I miss Fireworks so much. Nothing comes closer. Figma is great but web based and already shown willing to sell out everyone who trusts them.
I think you’re being a bit disingenuous here. Almost all packages are vendor and package prefixed yes, but your own code from very easily be as simple as:
namespace Me;
function test(){}
———
use function Me\test;
test();
Conflicting package names require you to be working on a very poorly written project (not using PSR-1) or a dependency that is even worse which is fewer and further between since composer.
It becomes a problem if you want to use multiple versions of the same library, which may happen if you are using composer, e.g two different dependencies uses the same dependency but different major releases.
It is valid. I’m running 8.4 and with autoloading etc it all works as expected. Maybe the language you’re arguing against isn’t the same language anymore.
That's it. I have been an acting/deputy brigade S6 on and off for years. Its more people and expectation management at that point than anything directly technical, but you are still expected to be an expert, like being a corporate associate director. I just promoted out of that and am looking for the next thing.
We currently use Metabase for SQL reporting, so I've been looking for something to allow actually changing values for a while. That being said, I don't think I would want to touch this. Reading through the code, it looks like a) it doesn't actually use transactions which I just find mind blowing and b) the first two files I looked at (api/database) has the schema for a database defined twice so already I worry about the data model of the app, let alone managing my own.
This is good feedback, we are working on adding in transaction support to the open source version. For what it's worth, our cloud product wraps everything in a transaction.
Semi-related but I needed a CAPTCHA on my site[0] mainly to block comment form spam and settled on repurposing a fun method I’d seen before. Is definitely not foolproof (or hard at all), but I really liked making it.
The site runs off of a tiny little server at home so I’ve got some very aggressive firewall rules. Anything from the usual bad countries, certain signatures etc are blocked. Reduced traffic to 1% of previous load.
I believe even a cursory examination of recent history to show your premise to be less than truthful.
There are bad actors. There are bad groups of actors. There are bad political regimes of groups of bad actors. There are countries made up of bad political regimes made up of groups of bad actors.
If you spend any time at all at a cloud hosting provider, you'll quickly learn there are only a few bad countries. It's not really Russia IME, it is mostly India and China. If you block those two, you're going to eliminate 99% of your abuse.
Cool, sure, good, probably not. I've never played Halo so I didn't entirely know what I was doing (do I shoot the blue guys too? it's not letting me through so I guess I do), and I don't doubt people couldn't even get what it meant by shoot. And god forbid anyone with disabilities that affects their mouse accuracy, or needs a screen reader tries to use it
Haven't looked at the devconsole but it'd probably be easily bypassed by someone dedicated.
Agree on the first part, but for the second... I think it depends on what your threat model is.
If you want to stop a dedicated attacker ready to spend time to attack your site, it won't work, but nothing will. If you want to stop a generic bot going over the internet and submitting all forms it finds with spam, this will work, and might even work better than wide-spread solution for which the bot has a countermeasure.
It has the advantage of being novel for the user rather than doing the same Google/Cloudflare/... CAPTCHA for the 10th time that day.
The last few point releases have been very stable, so normally within a week or so. Obviously this relies on having a pretty good test suite (we run ~8,000 tests in ~60 seconds so not too bad for us).
Is there a simple BOM for making something like this without a Car Thing. Would an arduino/rock chip with a tft touch screen work or does it warrant pi levels?
The computer is the easy part — any 10-year-old Android phone would do the compute part, and the networking part, and the screen part; and would be easier to program; and would cost less than pretty much any SBC kit.
The hard part (at a DIY level) is, honestly, the physical buttons and knob — wired as an input device to the compute without hogging the device's (likely only) port — and with good industrial design (no gross 3D-printed textures that easily get dirty from being touched a lot; no deep wraparound plastic bezel that prevents you from touching the corners of the display; dynamic-function side buttons thin enough to allow the screen to show the labels for them; etc.)
Right now you can get an Amazon Kindle Fire 10 HD for $75 - it has a screen ~3x the size of the CarThing. Spotify works out of the box on it. Same with Web Apps. You can put it in Developer Always On mode in about 10 seconds via the menus and it works great as a dashboard.
The actual Car Thing runs Linux on an Amlogic S905D2 (quad Cortex A53) with 512MB RAM/4GB flash and an 800x480 screen. So you could do something similar with pretty much any random cheap ARM SBC.
reply