Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×

Comment Re:Property values are more important (Score 1) 81

This. I keep hearing airy pronoucements about the importance of "corporate culture" and "collaboration" and whatnot, but in reality the conversations I heard back in the days when I commuted to the office consisted almost entirely of 1)gossip that would make a high school mean-girl clique look like Plato's Symposium, 2)placing and settling of sports pool bets, and 3)random content-free small talk.

Comment Re:Get rid of North America's 120VAC (Score 1) 290

The 110 is not created from 220. Both are created from the HV lines, usually around 7200V for residential areas. The transformer doesn't waste copper supplying 110. It's a center-tap on the secondary coil that splits the 220 into 2 hot rails. It would need the same number of turns for a 220 only setup. I guess the lead for the tap could be called a "waste", but it's a tiny amount compared to the overall amount of copper.

The complaint about conductor size for 110v is somewhat valid. However, that was chosen at the time and changing it would be a huge pain. That's why 110 circuits top out at lower amperage levels, usually around 20A. So the waste is smaller at least. I wouldn't mind changing new stuff to 220 only, but then you have 2 types of appliances everywhere, and will for decades. Look at People of Walmart and tell me what you think would happen then...

The ground and neutral serve different purposes. Cross-connecting them outside of the service entrance or omitting the ground creates an electrocution risk as it's quite possible to develop a voltage difference on the outside of the appliance as a result. Yes, it's a risk only in a fault situation, but it does happen.

The amount of copper you would save is smaller than you think, particularly compared to the overall use.

Comment Re:Cue the whingers... (Score 1) 349

These articles always bring the corporate boot-lickers out in force.

I really don't get what they get out of it, I guess they just like the taste of boot polish.

They're lucky that the bosses in the central business district will give them the experience a lot cheaper than Donna the Dominatrix in the red-light district.

Comment Re:Just delaying the inevitable... (Score 1) 250

Do you REALLY need to remember the IP of the DNS server though? If you have an address, you have RAs on the network. The RA can easily distribute the DNS IPs as well. So if you can talk at all, you can resolve names.

Sure, this doesn't help with servers you static assign. But in that case you probably have some documentation in front of you while setting up the OS. Or, for more fancy setups, something like Ansible. You could also just use SLAAC to start up, then use that to get the info to set up your statics.

IMO, if you can't handle IPv6, you can't handle networking. It's not any more difficult than IPv4, it's just different. As for firewalls, you don't need anything much. The default should be to block all inbound and route outbound. That's enough for home users that have no clue anyway. And they can "open ports" easily, at least as much as they could with NAT44. Which you can't do at all with CGNAT. The firewalls aren't complex for the users, they are pretty simple, far more so than NAT setups.

One thing I think they dropped the ball on is multihoming. NAT actually makes that easier, significantly so. NAT66 is a thing, and you can use it for that. You can also use NPT if you have static addresses, which most people interested in this are going to be willing to pay for.

Probably the biggest issue right now is moron ISPs trying to apply address starvation techniques that are required for v4 to v6 setups. There is no excuse for single addresses being assigned to home users. A /64 should be the default, with at least a /60 available with no issues. More than that for home users is unlikely to come up, but it would be nice if they made it a paid option at least. Yes, a /64 is a LOT of addresses, but it's only 1 subnet. And with the amount of addresses available, we will all be long dead before it's an issue. And subnetting less than a /64 causes lots of issues, and completely breaks all Android devices.

For those that really do want NAT, use it. NAT66 is commonly available on many platforms. I think it's stupid, but whatever. It's another tool and if you like it, use it. You can even use global addresses internally since ULAs are broken in dual stack, and just not route them outside, requiring the use of the NAT. Or NPT which requires less state tracking and router/firewall resources.

Comment Re: At least give a reason (Score 1) 230

It's highly unlikely that the best people are the ones who prefer an environment (the traditional office) where looking busy and management by walking around will enable you to get by rather than an environment (remote working) where extraneous elements are filtered out leaving only performance.

Comment Re:Remote is less rigid and limited for communicat (Score 4, Insightful) 230

All my experience suggests the exact opposite -- it's much easier to send a suggestion over a text channel than in person, with less downside risk (sending a "no" message back leaves much less of a lasting negative impression than the feeling that someone is wasting your time in person).

Comment Re:Why do they want people back in the office? (Score 1) 97

Several factors:

1. Some of them are old dogs unhappy about having been forced to learn the new tricks of managing a remote workforce during the worst of the pandemic, and think they can just make it go away and return to the BeforeTimes.

2. Some of them get emotional charges out of being able to boss people in person (or, somewhat more benignly, from having people around in general).

3. Some of them have economic interests in commercial real estate (e.g. the banking industry) or are influenced by people who do.

Slashdot Top Deals

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...