I'd argue that none of those are technology companies. We call too many companies that use computers technology companies.

Sure they use or even develop software but it's for their own internal uses. They do not develop technology as an end product to sell. They sell a service.

Python is a strongly typed language, and to call it untyped is simply incorrect and a bad assumption. Python is dynamically typed, so the interpreter determines types at runtime instead of compile type. But, to say it is untyped, well, is wrong. Python became popular for three reasons: built-in collection types (lists, dictionaries, sets), support for functional, imperative, and object-oriented paradigms, and finally, it is easy to integrate with existing libraries. Collection types are a big deal because, prior to Python, most languages only offered simple types and fixed dimension arrays. To implement useful data structures that could scale to handle large amounts of data, like linked lists, hash tables, trees, and sets, one had to write lots of plumbing code - comparisons, swappers, whereas with Python, you could declare a list and start list.append()ing away. Python also made it possible to write loops without counters and breaks, which was very different than most languages at the time (for thing in things instead of for thing = 0, thing ++, thing200). A lot of the popularity in AI comes from managing data with collection types and calling faster code (that usually runs on GPUs). For a developer, you get to an acceptable solution faster. For a user, it's generally fast enough. When it's not, you can always write it in C and call it from Python.

Sure you can update the phone, but the phone won't keep user data unless it's been unlocked.

The only avenue of updating and keeping the user data is to unlock the phone then update. Apple has purposely made it so that there isn't a backdoor.

They know the numbers that they assigned to that line that the call is coming from. Anything not in the DID list shouldn't complete that call on that line.

While a cell phone number might be a legit callback number for that person the phone company providing the T1 doesn't know your cell number. At this point any call outgoing should send the caller id information to be able to call back on that number. Spoofing has been abused too much. Same with email address spoofing. Both have legit uses but their abuses outweigh the usefulness.

Exactly ipv4 needed address extension and simplification. People have a hard enough time understanding VLANs and subnets. Let alone trying to figure out how to calculate how much I can works.

This is one of the things that drives me nuts about IPv6 proponents. They go all crazy defensive if you criticize anything about their protocol, even when the criticism is fair. I haven't seen anything from you that isn't fair and I have seen the opposite from jd.

It's a fact that IPv6 is much more complicated than IPv4.I would have just made a new protocol that corrected IPv4's mistakes, addresses would be 64bit long and used CIDR notation. Broadcast would have been kept since it's stupid simple to use the last address, with all FF's for the MAC. DHCP would still exist and would be the main way for a dynamic addresses would be assigned Dhcpv6 has a cool feature, a router can request to get a routable subnet.

IPv6 has two main mistakes. Trying to do too much for the layer it is in the network stack, and not learning from past mistakes.

There is this season called winter that makes features like all-wheel drive and higher ground clearance make a lot of sense. Combine that with five kids and car seat laws requiring everyone up to 10 years old be in one, and you have the perfect sales storm for larger SUVs.

This is really the shoe being on the other foot. Jobs were scarce a few years ago... you could expect 7-8 candidates at a minimum for every job you advertised. Now, it is less than one available job seeker per open job so you have to really change how you treat candidates if you want to hire and retain. That includes pay better, especially in unskilled and semiskilled roles which are the hardest to hire right now.

This is one of the things that eventually forced me to shutdown Facebook for good. I got sick and tired of seeing the same posts over and over. Then I'd switch from "most popular" to "newest", and what do know? There were tons of posts that I never saw because Facebook declined to include them in my feed.

Just let me see what I want to see, not what you think I should see.

Touchscreen Chromebooks have been running android apps for about a year or so. ChromeOS has a full strength, desktop grade browser which is a much better experience than any mobile browser. Android apps are surprisingly good on ChromeOS now... Devices like Samsung's Chromebook Plus are basically what tablets want to be when they grow up. The bonus is being able to run Linux, and by adding container support, it would make that experience better and potentially much more secure than running crouton. One of the best features of ChromeOS devices is how easy to manage and restore they are compared to "full strength" OS devices.

This is a great tool if you want to increase diversity. Sure it can be misused, but if you read the context, the article is trying to suggest congress make Facebook liable for the actions of their users. How does this actually fix anything? How is this different than making gun manufacturers liable for misuse of their products or auto companies liable for misuse of their products?

No it's not.
Don't confuse a reasonable wanting with unreasonable wanting.

The elephant in the room is that we are building on almost 50 years worth of insecure software that runs on insecure hardware on even less secure operating systems connected to an even less secure network... Honestly, it is amazing that all of it works, let alone be as secure as it is. Safe by design languages are going to help a lot, but it will take 20-30 years for enough of the stack to be rewritten.

Software PMs get a bad rap because the use case is often to be a buffer between incompetent management and a misguided and badly staffed development team (usually because of incompetent management). PMs pay for themselves x2 or x3 by making it possible for the devs to get done on time, under budget and often with fewer defects - if they can actually practice their craft.