Next.js has introduced some keywords such as 'use server' and 'use client' that you enter in the file at the top. Much like 'use strict'. If you attempt to use server code in a client file for example, it will get caught by the ts compiler / Linter.
But for sure the lack of clear lines for where the server ends and the client begins has always been a pain of these kinds of framework offerings.
Not just accidental inclusion but intentional insecure inclusion. FE developer gets a BE ticket (because why not that's the whole point right?) and forces something through all proper-channels leading to trusted (server) code running on the client.
I lost a Mac laptop in the pre-MagSafe days, to a bullpen environment –a sysadmin was rushing to a meeting, snagged his foot, and took the cable and the laptop off the desk at high speeds.
After that, I was a big fan of MagSafe, but today’s USB-C and better batteries situation solves a lot of problems that MagSafe did in a different way. It allows for you to have multiple reasonably priced chargers, so the one on your desk can be safely placed, with a short unsnaggable cable. And you can still go to meetings and take your laptop home – because you have another cable in your bag and another at home.
So these days, I barely use the MagSafe cable on my MacBook Pro.
I agree with you, but in practice I've never had a problem with USB-C at all and everything mobile I own has USB-C except my face trimmer, and the next one will be USB-C for sure.
If you're worried about the port in a classroom environment you can use a short extension that you plug in on the device end, it will make the connection separate much easier if something unfortunate happens.
I really don't think this is a good idea. There's already enough digitisation with physical back up in this situation. I think this is a case of not fixing something that isn't broken.
This is also quite scary.
> airlines will instead be alerted when passengers arrive at the airport and their face is scanned.
British-born here. Standing on a plug is somewhat a rite of passage that each kid goes through at least once. It's a meme in the UK.
The flat back of most plugs increased the risk of standing on this type of plug. It's similar to the experience of standing on Lego, except it will dig much deeper into your foot, and falling over is better than putting all of your weight on it.
It can be a common occurrence, because using an extension cord or an appliance you don't always need to have plugged in can just be laying around. And kids aren't known for being tidy. If you managed to get past being a clumsy kid and had the self awareness to avoid it, props to you.
This reminds me of the time I just learned how to write .bat scripts for Windows, when I was a teenager.
The power of being able to send this file via msn to a friend, convince them to open it, and then get a full message in capitals of "YOU HACKED ME! MY COMPUTER IS BROKEN!" Before watching them go offline (the script shut down their computer after 30 seconds) was a real heart racer. I am sure it contributed to my interest in computers in the following years.
This was a lot of fun to read and really tells the story well. I am thoroughly amused. Thanks for sharing this!
This article taught me nothing about managing people I can't fire and I was really hoping to take something from this. I've had this happen before (and it may happen again) so I'm disappointed that this just ending up being "if you want to fire someone, and your boss doesn't let you, you'll probably quit".
It taught me that some managers feel that they're absolutely 99% right when they feel like firing someone. Managers are so good and firing is so hard that managers only feel this way when it's 99% justified.
But for sure the lack of clear lines for where the server ends and the client begins has always been a pain of these kinds of framework offerings.