afloatboat

Sad to hear that about the PS3, seeing how long it took them to go to market.

Been driving a Polestar 2 for nearly 4 years now and while it’s not a disastrous experience it could be a lot better. Things have improved over the years, but still pretty disappointed.

The infotainment system runs on a very outdated atom chip that’s too slow for Android Automotive. Constant frame drops, crashes or stuff just generally not working.

In a recent software update they disabled the cockpit view if you put it in reverse, just to save on resources.

The whole Android Automotive thing is worthless. There are barely any apps and when they finally released YouTube after 2 years it was just a buggy wrapper around the mobile web view. Most videos will just display a green screen due to lack of codec support, so I just pull out my phone now when I’m charging. But even the radio or Spotify fail to play half of the time.

The 360 degree camera sometimes will just not work. I still have a tiny back window, unlike the Polestar 4, but the reverse lights are so tiny and dim that it’s impossible to see anything when reversing at night.

Digital Key works, but also have to regularly pull out my phone to trigger it or manually press the button in the app. If you’re in a parking garage without internet you’re simply not getting into the car. And that’s without the random logouts.

Lane assist works relatively well, if it weren’t for the constant nagging to put your hands on the wheel even if you’re lightly tugging it. I need to really jerk it a bit before it stops beeping at me, making it completely useless.

Maintenance happens at the Volvo dealership where they made sure to make me feel like a second class citizen for not leasing a Volvo. They didn’t read my reservation mentioning the broken rain sensor, ensuring I had to return a week later for them to replace it because they didn’t have the part in stock.

I was between a model 3 and this car initially. Mainly because of the software, and for that reason I still regret not going for the M3, but given the current situation I’m happier driving the PS2.

Nearly 4 years in the chipset is still the same for the newer model.

I got a loan for a house 2 years ago. The process included showing our 3 last pay slips, the expected cost of the house (new build) and showing the bank how much money we had in our accounts (I loaned at a different bank that gave me better rates). There was a base percentage that lowered based on your level of income and the ratio of own contribution/loaned amount.

I live in a Central European country.

Next should have the same functionality that Gatsby had when doing a static export: pre-optimised images for different breakpoints that are created at build time. That would be a truly portable solution.

SVG elements also support currentColor for the fill property, which is linked to CSS’s color property.

<svg><path d=“” fill=“currentColor” /></svg>

element { color: hsl(0 0% 0%) }

One advantage is that you can target the parent element and the SVG will change automatically.

You can also create multiple “shades” by having currentColor on multiple paths with different opacity.

Don’t get me wrong, I was just making an observation about a ‘role’ being specified. Not suggesting the role=“application” should be used here.

Ultimately in my case I’m leaning to either replacing the production year, parental guidance and IMDb rating with a dl or prepending sr-only titles to the individual tags.

I tested the page with VO on Safari and got the same results as on Chrome. So the good thing is that in practice the current setup appears to be accessible, but it’s frustrating that the theory seems to be different and just not clearly defined.

I can't link the page, but this is a cleaned up DOM output (the extra spans/divs are components):

`<div><div><span aria-label="IMDb rating" title="IMDb rating">IMDb 8.2</span></div><div><span aria-label="Parental guidance" title="Parental guidance">12+</span></div><div><span aria-label="Production year" title="Production year">2007</span></div><ul aria-label="Genre"><li><div><span>Romance</span></div><li><div><span>Comedy</span></div></ul></div><section><div><h2 id=":r1j:-cast">Cast:</h2><ul aria-labelledby=":r1j:-cast"><li><span>ABC</span><li><span>DEF</span><li><span>GHI</span></ul></div></section>`

`section ul { margin: 0; padding: 0; list-style: none; li { display: inline; &:not(:first-child)::before { content: ", " / ""; } } }`

Pretty clean, I like it.

I tested it out on a page I'm developing that has some meta data on a TV show. One of the elements is a set of divs each containing span with an `aria-label` describing the contents. With MacOs' VO this gets called out correctly, and Chrome's Accessibility Tree also picks this up, but this tool doesn't show the `aria-label`, it just shows the separate values as strings one after another.

It also picked up a `::before { content: ", " / ""; }` as `, value`, but that's not supported very well in general.

Not if you consider that a lot of front end developers today started learning web development through JavaScript.

I started around 2000, when people were still using tables for layout and CSS was pretty new. If you wanted interactivity you relied on the built-in tools on the web because there was no other choice (apart from something more extreme like Java applets or Flash).

Today’s web developer starts with something like React, learns JSX instead of HTML and doesn’t need the form tag or checkboxes/radiobuttions/select because they have useState, onClick and className to highlight whatever they think is active. I’ve been working as a React consultant for +6 years now, and every PR I see has the same issues.

I wish I was lying about the onClick on anchor tags, and for primary navigation it’s usually done right. But once they see a block link that contains multiple components (a “card”) the mind always seems to jump to onClicks that call navigate.

A more advanced error is when something is an anchor, they correctly implement the a tag with an onClick and preventDedault, but they forget to check if the user is holding down shift, hyper or control or if they pressed any other than the primary mouse button to try and open the link in a different tab/window.

Semantics in general is a lost art as well. A Text component that only returns p or spans is used for titles, they don’t consider hierarchy at all.

To be fair, there is so much logic in the client now that I understand that people with different ambitions have taken an interest in it. The only problem is that companies just blindly hire for front end developers without considering the different expertises.

I think this is the root cause for a lot of the complaints HN has about JS. I want to build good UI and UX, but there’s so much other work and configuration that I’m expected to work on, in a limited timeframe to not ruin my velocity that I just never get to it.

I wish! I love working with HTML and CSS, but every front end job is covered by the blanket term “front end” that considers you as much a JavaScript ‘architect’ as they do a UI developer. Not realising that this does not make the slightest sense.

Can’t tell you how many times I’ve had to tell experienced developers they should use anchors to link to other pages and not an onClick. Those same people are much better in architecting then I will ever be, yet technically we have the same job description.

As an unhappy front-end web developer I feel I'm mostly unhappy because my job title has stayed the same, while the responsibilities have changed drastically. I've always been a developer that liked to work on the UI. I got joy from creating good looking and feeling components, going the extra mile in terms of small animations and tidbits to make it feel just right. As the years went on JavaScript played a bigger part in that, so naturally I picked that up as well. But I still only learned JavaScript to enhance the visual components that I was building.

Now, n years later I can barely work on the graphical side anymore because most of my time is spent on writing business logic on the client. Fetching data from the server, parsing and massaging it, data management, … So I've basically become a backend developer for the frontend now.

The visual part of the web has been taken over by tools like Webflow and Framer or the other extreme with ThreeJs. I recently talked to some companies/recruiters just to casually see what was available and my desire to go back to the more graphical/ui/ux side of things, but everyone was just looking for a 'react developer', so just the same boat that I'm in now.

So yeah, I power through, but that doesn't mean I'm happy about it. I'm also not completely unhappy, but things could definitely be better.

Raycast

- Replaces Spotlight for opening applications

- Replaces Magnet for window management, same features but don’t have to run a separate app now.

- keeps a clipboard history

- allows me to convert colours and units

- integrates with my calendar to show me upcoming meetings, shows them in my menu bar and lets me join them with one click

- allows me to prevent my Mac from sleeping (for certain durations) with caffeinate command

- has a variety of plugins available

Probably forgetting a lot of things I use it for, but even without the premium features I use it all the time.