"But we benefit from being able to hire good people"
Probably the good people the return to office lot lost.
33064 publicly visible posts • joined 16 Jun 2014
One instance given was that supposed efficiencies were due to the fact that the WFH employees were working longer to get the work done. The true comparison should have been between the WFH extended hours vs the total employee WFO time of office hours plus commuting time.
One thing that gets conveniently overlooked in these discussions is the time that commuters are donating to employers without charge. My worst case used to be at best an hour & a half each way, door to door, High Wycombe to central London. 15 hours a week, equivalent to about 2 full days per week of my time life unpaid for several years.
Having spent time working without commuting staff now perceive that the cost of it, not just in fares but in time, has fallen on them but benefited their employers and that it really wasn't needed.
If, in fact, employers were to pay commuting staff for the time spent commuting then efficiency of working in the office would be seen to be much lower. The challenge for employers now is to work out how to achieve whatever benefits they see to working under one roof without excessive commuting; perhaps dispersing offices to suburban hubs.
"it looks very clean and remains quite intuitive"
It looks ugly. Black icons following the trend of looking as if a cuneiform writer has attempted hieroglyphics on dark grey is not a good look.
If you were using it exclusively you'd at least get to know the icon set. The trouble is that when something built on this framework, say pdf-arranger*, is installed in another environment it can't respond to whatever icon theme (nor colour theme) is in use and the responses of the system menu button are idiosyncratic. Consequently it's not really intuitive at all.
* The only one so far I haven't been able to avoid.
House name carved in stone 6" high letters next to the road and drivers still used to have problems. Fair enough if they're coming down the road because it's not so easily visible then - but we've had at least one delivery to a neighbour from whose gate our house name is perfectly visible.
And the there's the TLA delivery company which give its drivers GPS coordinates but refuses to give them the correct ones even after emailing them the Google StreetView link clearly showing that stone and from which they can take the real coordinates. As far as I can make out the drivers aren't even allowed to stop the van other than the TLA's location so the those who know the house have to part there and walk up the road.
"Down hill: turn left at the T junction, past a field on the left, first house round the corner; Up hill: second house on the right past the farm" would be far better.
"Many shop owners would live upstairs but in many cities, they've passed ordinances against that "
I keep saying that the present mess was actually planned. It wasn't planned to become a mess but that was the result of well-meaning post-war legislation to separate living and working space. It was built to avoid the slums built round sometimes heavily polluting industry. What happened was that commuting replaced heavy industry as the polluters.
"Having those folks back in the office will be very important for our restaurants, our coffee shops, our dry cleaners."
What happened to that great American entrepreneurship? Their customers might not be coming to them any more so why not go to their customers? Open chains of suburban dry cleaners. Start mobile catering.
And repurpose those redundant office buildings as residential. The huge city centre drawing in commuters from more than a thousand square miles of its surroundings isn't sustainable for the future. That needs to be realised and accepted. A city offering a balance of workplaces and nearby accommodation who want to work in the office is OK but that's going to support very large workforces in the office.
The GPL is bothered with more than ensuring that the software's source code is made available to the customer/licensee. It's bothered about it being made available with the right to redistribute without further restrictions.
That is written into the GPL, including an obligation not to impose such restrictions on those to whom copies of code are supplied. The question here is whether the business relationship under which RH provide GPLed code implying such a restriction on their customers.
"I find it hard to understand who is inconvenienced by these moves."
You mean apart from those building the Rocky & Alma downstream distros?
1. Companies who use RHEL in production because they need support* but who also run a downstream rebuild for training, testing and/or development boxes because they don't need support on those. Are they going to have to pay more for those secondary functions? This is the risk for RH. If the matching downstream builds aren't available those customers are going to have to reconsider whether RHEL is still the best choice for production.
2. The certifying** application vendors who certify against RHEL because its existing place in the OS market has made it a valuable market place for applications. If this makes their customers wish to look elsewhere they are going to have to do the same. The testing against a platform is expensive. Maintaining multiple versions if testing reveals that's required is expensive***.
3. The customers of the vendors of the certified products who might not have a problem per se with running RHEL but will have one if their vendor switches platforms.
* Support is what provides the customers' perceived value for money.
** In regulated application areas certification of the S/W they use is an external requirement that the customer needs to meet.
*** "Inconvenience" isn't the issue; it's the cost.
"Obviously this is not expressly written into the GPL or in the RHEL software licence."
What is expressly written into the GPL is that (a) it applies to derivatives, (b) the recipient of GPL code, if redistributing it, is bound to pass on the GPL with the code and (c) is not allowed to add further restrictions if they do and (d) is entitled to remove them if they have been added.
In this both Red Hat and their customers are recipients. RH as a recipient is bound by the GPL and if it modifies the code the resulting derivative is still covered by GPL, must provide the modified code if required and should not add further restrictions.
The question is then whether these contractual terms for RHEL are an implied further restriction.
That "Reading Comprehension 101" is certainly needed because it's very clear indeed in the context that the company is Red Hat. In case "Big Purple" went over your head IBM which took over Red Hat is often referred to as Big Blue and, as mixing red and blue gives purple, the resulting amalgam is commonly referred to hereabouts as Big Purple.
"Perhaps if it could hover the names of my colleagues in meetings and exactly what they do"
What they do as in:
Jobsworth
The only person in the room who knows what's going on
Sheet anchor
Here with their own agenda about something else entirely
Sent along because their department has, in their view, to be represented but doesn't have a clue what it's about
Has to sign off budget
Etc.
Brookes, he of TMMM, also published a book "The design of design". Part of this was recounted his university research group's work on this years ago. They discovered something very similar - its appeal to users was limited. IIRC users were much less keen on being able to walk round inside a VR model of whatever they were designing compared to having an image of it in front of them that could be rotated or walked through, something for which an ordinary screen would suffice.
"and every bloody time when a meeting is over it asks me about the audio quality"
Ah, yes. The post-service survey.
I think there's a gap in the market here. A site the customer can use to send a survey to the vendor asking irrelevant questions about the customer's completion of the post-service survey.
"f I could demote that interest in Topics, this may actually be useful."
It would not only be useful to you, it would also be useful to washing machine sellers because they wouldn't then waste money by spending it with the advertising to place irrelevant adverts. So it won't happen.
So many places treat an email address as an ID. This is stupid on many levels, this being one of them. It's a destination for communications. It shouldn't be anything else. It might be an issue that's tangled up with this one but it's a distinct problem in its own right. In such circumstances if the ID is important then the email address should be one over which you have better control, ideally your own domain with a reliable MSP. Worst case you can change MSP.
ISTR that when 5G (or was it 4 or 6 or whatever?) being mooted it was said that because the range was so small the base stations could be like WiFi and instead of erecting the sort of masts they're now putting up they would be many unnoticeably small boxes similar to WiFi base stations on lamp-posts etc.
This morning I went to give a wheel-chair bound friend a lift. Being built on a steep hillside the bottom of her drive is well below road level. While waiting for her to manoeuvre out of the house I happened to look up & realised just how over-towering the newly installed 5G mast is. It's just over the garden wall but the garden wall is a retaining wall against the road so the effective height is getting on for 30m.
They are monstrously intrusive constructions. Their designers should have been sent back to their drawing boards CAD screens and told to start again. Forget brain frying & spreading Covid nonsense - aesthetics are a completely adequate reason to object.
"In my very first full time job, the offices were repurposed chicken sheds (don't ask me how they ever got the smell out - it was done before they were sold to my boss.)"
My late cousin's garden shed came from a chicken farm. It still bears a residue, not of the chickens, but of shrapnel. A factory about a mile away was the presumed target for an air raid - reputedly at one time it was the only one still standing machining certain parts for Spitfires. The factory was missed but the chicken farm got a direct hit.
"For those who are clinging on to the idea that Linux is somehow going to successfully avoid being absorbed (for all practical purposes) by big business, this is just another reminder of how things are slowly sliding away from them."
See the posts by Ian Mason & thames above.
What could happen is that the Linux market slips away from RHEL.
Any business using RHEL in production & several CentOS/Rocky/Alma instances elsewhere is going to be reviewing its situation next week: is it cheaper to buy all the extra RHEL licenses they need once those work-alikes are unavailable or to move. As part of that they'll be talking to any application vendor who currently only supports RHEL and who consequently will also be reviewing their situation.
Also, expect Suse and Canonical to start pitching to application vendors PDQ.
"They'd have to sue you, and that's different. Defending yourself is not the same as bringing suit against a big, deep pocketed company."
To which the response might be cease and desist letters from various copyright owners for being in breach of the licence for the software they're distributing.