buzziebee @ buzziebee @lemmy.world

Posts

0

Comments

123

Joined

2 yr. ago

I'd rather have 30 incredibly intense and productive hours than 60 completely chill no stress do a little of this a little of that hours.

My old job was 60-70 hours of incredibly intense productivity (was working for a Japanese corporation) and I learnt at a rate well above what other workers would due to the intensity, but then I had a breakdown from burn out. Keeping that tempo for fewer hours is the best of both worlds. Employers need to be focused on output rather than time logged.

I'm actually a big fan of how they've standardised the design language and accessibility requirements across services. This "why" box that a couple of comments are criticising are likely so they can continue to improve accessibility.

Firefox performs as well as chrome 99.8% of the time. The problem is chromium keep implementing things that haven't gone through the spec process fully yet. This causes the following situation:

The other browsers don't implement half baked privacy violating features which Google decides will be a new web API despite objections. Developers build features on their sites using that half baked crap. Users try to use the new features on Firefox and kick off about "Firefox specific bugs" because they haven't implemented non standard APIs.

Safari is its own kettle of fish though and causes a lot of drama. Recently they've caught up a lot in terms of support for most standard features developers want. However there's a big issue with supporting iOS Safari - it's version is tied to the iOS version of the phone. So users with older phones will be stuck forever on older versions of Safari with breaking bugs for things like flexbox. If you're in a market with lots of older phones then you have to spend a lot of time ensuring you support that older browser version. iOS Safari is the new internet explorer.