160 karma · joined August 19, 2016
The original commenter was taking a dig at MacBooks, and I'm calling him on it - where does it say that the Pro will operate like this, and do any other laptops do it? Neither of mine seem to, and my work Dell doesn't either as far as I know.
If the lid is closed, you need to use an external keyboard (obviously). If the lid is open, you can choose to use either the built-in keyboard or an external one. No one ever said you couldn't use an external keyboard. The OP wants to use the built-in keyboard but not the built-in screen (i.e. the screen should be off). The commenter seems to think that it's an intentional anti-feature that is only available on the Pro model. I believe that there are no laptops that do this, and I wouldn't personally care to work that way even if they did.
So to answer your specific comment, the user is always free to use the built-in keyboard or an external keyboard. Unless, of course, the lid is closed - then you pretty much have to use an external keyboard.
That said, the phone is definitely usable - as a phone and probably for texts and many other apps. But if the 2-4 year lifespan of your banking app is the issue, maybe just use it on the desktop or through a browser instead of the dedicated app. As long as you can get a recent-ish browser installed on your phone, you might be able to use the web banking interface (not all banks have mobile-friendly versions, admittedly).
And yes, I believe the official stance of Google with regards to updates is 2 years of updates followed by 2 more years of security-only updates. Other manufacturers may do less than that, which is one reason I get the Pixel phones.
Why do you feel you need to change phones every 2 years? The hardware is probably fine unless your carrier of choice completely changes their network. The software will still work, although security fixes might be less frequent (it seems those are done for about 4 years, though 3rd-party distributors like Motorola might not honour that).
Are you sure your perception that you need a new phone every couple years isn't being driven by marketing and contracts?
As for "spin," something like learning what you dislike in a position or company, or how your current position has reinforced your passion for the position you're applying to - things with intent between the lines are fine. Avoid saying anything like "I needed the money" or "that place sucks so bad."
Above all, learn from this (of course). Was anything weird during the interview and hiring process that you can see in retrospect was suspicious or misleading? If they had said one extra sentence in the job description, would it have tipped you off that the role was a bad fit? Is it really the job or is it the people that are a bad fit?
For those who don't realize, Angular 12 was released in mid-2021, less than three years ago. Even if the company meant Angular2+, that was still only released in 2016, less than eight years ago. I asked if they meant AngularJS (originally from 2010), but no, their requirement was 10 years with "new" Angular. I informed them they would be looking for at least two more years, but good luck anyways :)
I've seen the same type of request for React as well, with one company somewhat ridiculously asking for 15+ years of React experience (it's less than eleven years old).
I think the quality of technical recruiters has taken a hit in the last half-decade or so.
Now I get emails from at least a dozen services several times a week saying I'd be a perfect fit for positions that are in-office but not in my province (or even country sometimes), that are not things I'm interested in (retail lead in a piercing shop, for example), and are not things I'm even remotely qualified for (chemical engineer has popped up a couple of times, weirdly).
Not only do these systems suck, they're invasive, annoying, and counter-productive to the job searcher in many cases. If I could only have "guest" access to apply for that specific job....
The problem with React - and to a lesser extent Vue - is that each project will likely use different libraries for similar functionality. There are some very popular defaults for many (like routers), but you'll still end up needing to be familiar with more than one.
You could look at Next.js which is a React-based framework.
Between Vue and React, I'd go with Vue. It has the same problems with multiple options for every framework aspect, but most of it is Vue-branded (so to speak) which means you're less likely to need to learn alternatives. I also think it makes more conceptual sense than React, but that's a personal opinion.
If your interest is to become employed, React is definitely more popular - but it's not better.
Newer versions of Chrome do a better job for me, so I recently switched to Chrome for daily usage, and Edge for testing.
This boilerkit is worth $39 to me because it would definitely take me longer than a couple hours to build myself. Someone else has already put in the 100 to 1000 hours to make it a decent experience.