Your hands are not in the center of the keyboard in the base position either.
I'm seriously asking, I have no idea right now what the more ergonomic option would be.
5,004 karma · joined January 29, 2016
Your hands are not in the center of the keyboard in the base position either.
I'm seriously asking, I have no idea right now what the more ergonomic option would be.
This could become a nice Rorschach test, where eveybody can come to different conclusions based on which metrics they pick as important.
People only read the headline and get triggered, not even the tl;dr can reach these humans anymore.
Many (of the interested) people in the EU are unhappy about some democratic shortcomings of the EU. The only directly elected body is the parliament and it is not very powerful. There is too little power at directly elected bodies and too much power at elements, that are far from the voters reach.
At the last election they wanted to address that and promised that the lead candidate of the party with the most votes will be the commissioner.
That didn't happen. Instead we got vdL, who was in trouble as Minister of Defense in Germany for some hiring consultants without proper process and for ... deleting messages from her phone.
The whole situation is extremely painful for people like me, who support the EU. The tone-deafness, the disrespect for the voter. It is painful.
Wikipedia makes no mention of that reasoning: https://www.wikiwand.com/en/Roll_program
The roll is part of the gravity turn, every craft does that kind of stuff to 'aim'.
For C and C++ code you want to be able to build with different compilers.
I think that also makes sense for Rust, the language and the compiler should be two separate things and there should be multiple compiler suppliers.
Are there arguments why this would be less relevant for Rust than C?
How often are you bitbanging non standard protocols? And if so, which field are you in?
I think you can easily do 90% of iot projects with this. Which means you have more time for the 10% of projects that are actually hard.
Using Arduino will not magically rot your brain and make you unable to ever learn other things. It will however get you started quickly and therefore give you an in. I started using Arduino in a student job, then used Micropython, did my masters thesis on using Micropython on cubesats and now I run a team of 15 hardware engineers.
All of this happened because I got started with easy beginner tools. There was no one to teach me the "real" way. The people preaching the real way and railing against simple beginner stuff usually don't write tutorials, build easy to use devboards or write easy to use libraries.
They are expensive, but I also don't hate it. If we can reduce the impact of infrastructure on people, we should do it.
The thing you are hating on is pretty much this file: https://github.com/arduino/ArduinoCore-avr/blob/master/cores...
Arduino is C++ with some boilerplate and a library.
My monthly income goes to (very roughly estimated):
* 35% rent * 10% groceries * 10% other stuff (energy, internet, subscriptions) * 10% mobility * 35% savings
My rent didn't go up. Not sure if savings are part of inflation (how do you measure inflation for ETFs?). So only 30% of my income is affected by inflation, which is less than half of my spending.
Your personal inflation rate will mostly depend on if you live in a new or an old building (e.g. my heating costs are tiny because the building is new) and if you have a car (I only have a motorcycle and I take the bike to work). If you live in an old house and have to drive a fuel-inefficient car to work every day, you are screwed.
I think the current inflation is mostly about energy prices and only very little about money supply.
Many languages (if it is AOT compiled and uses LVVM you can probably get it running on a uC) have POCs for running on an a uC, but often lack the HAL (libraries to use all the peripherals).
CircuitPython is very nice for beginners, Adafruits tutorials are gold. Switching to MicroPython is very easy (CircuitPython makes some simplifications to be more beginner friendly, MicroPython aims to be as "professional" as possible).
There is some steps necessary to go from "prototyping MicroPython" to "production MicroPython" and many people either forget about them, are not skilled enough to do them (which is fine, MicroPython is about onboarding people to embedded as well) or they feel like these steps make using MicroPython pointless.
Literally the choice of glue can make a huge difference for ease of repair with no impact on the design.
Also e.g. the Pixel 6 has an element in the display assembly that makes the repair easier + a glue that melts well.
Older iPhones were also easier to open, but their glue gets seems to get more aggressive each year.
The whole access via glued display construction can be fairly easy to work with when the display assembly is done right and they use a glue that melts well.
And sure, the even easier access design around screws is harder to do, but also possible. See the iPhone 6, which used screws and a much weaker glue.
If Apple wanted to they could make an iPhone that people love and has all the features they want and be much easier to repair then the current version.
These trade offs are far sampler than what they want people to believe. Apple has the budget and the talent to do it. They don't because they don't want to. //edit: also screws are not the only option, see Pixel 6 which doesn't have screws but still makes it easier to open up the phone.
That's fine and that's their right, but we should call it what it is, and not act like a screw is something impossible to design.
I can't go through the whole order process because I don't have an iPhone IMEI, but to me it looks like you can just buy the parts you need.
I pointed out that the conundrum of repairability vs. quality is made up, or at least dramatically overstated.
There is currently only one company that I know of that focused on repairability in their phones (Fairphone) and they have a hard time competing on other factors due to the fact that they are tiny.
Now your are going to say that them being tiny means nobody wants repairability. Then I'm going to say that people do, but it's just one aspect and that the phone is lacking in others. Then you are going say that this means you can't build good repairable phones. To which I will say that you can but nobody but one small company is trying. At which point we will be stick in an endless loop.
Truth is, if Apple really wanted the could design their phones in such a way that you could open the back with a couple of screws go replace the battery, but they have no motivation to do so and instead prioritize other aspects. 99% of the industry does the same.
1. The repair kit described here is not mandatory for anyone to rent to be able to buy the parts. You can just buy the parts alone and use whatever tools you want. If you attempt your own repair, you should use the simple ifixit style tools, and understand the higher risk of damage you are taking.
2. The kit described in the article seems very decent for any kind of independent repair shop. They will probably already have pretty much the same setup.
3. Right to repair is about access to documentation and parts. Nobody epects anyone to make it easy for the user to replace 512 pin BGA part. Right to repair does not mean that it should be easy to repair something, just that there shouldn't be artificial obstacles and that there should be supply of documentation and parts.
4. Repairability is still an important topic and with discussing, but it is a separate issue from right to repair. E.g. I think phone makers could make replacing batteries much easier and that it would be a much smaller design compromise than some people like to claim. But that is a different topic from the baseline of right to repair.
To me this seems like Apple has a good basic right to repair offering both for individuals and independent shops. This article is bad for the right to repair movement, because it doesn't understand what it is asking for.
Parts. Documentation. No artificial obstacles.