I use a Quest 3 + Immersed software and code 6+ hours a day like this. One giant 50" monitor + 3 support ones on the sides. Best "monitors" ever.
I love that I have no eye strain at the end of the day.
It must be a Quest 3, not the 3S - it must have the pancake lenses, the old ones only focus well in the centre.
Do you have an opinion on how close the Quest 3 + Immersed can get to replicating an 8k 54" tv at 36" away? I know the VR panels are ~30 PPD (and there's other issues) and I'm asking for something that's ~60 PPD. But does blowing up the screen 50% work? (Or changing the aspect ratio, keeping the same pixel count and still scaling.)
MacOS just doesn't really play well with non-retina text anymore. I think windows/linux probably has clearer text at lower PPDs.
I can only describe my setup, have never tried an 8k monitor.
I am guessing I have about 40 PPD. I still have a sliver of space on each side where I see part of my support screens (vertical 1080P on each side). It has a 110 degree horizontal FOV.
My main screen is driven by the MacBook Pro's native resolution (3456x2160). Immersed can create 4k virtual screens, but I don't really see an improvement, the Quest's panels are the limiting factor.
Not crisp like retina, but the size makes up for it. In very rare cases I just lean right up to the screens (they are 3 feet from me). As the focal point is somewhere 4-5 feet away, you can have your face right against the screen to see tiny detail.
Also the fast refresh (I have mine set to 120Hz) matters. I tried my work's Vision Pro. Yes, more crisp graphics. But it gave me motion sickness, there is a slight motion blur, the pixels don't seem to refresh fast enough. The Quest is rock solid, never felt unwell using it.
I see. So it sounds like you have the MBP set to the non-retina setting then passed to quest via immersed? (ie if you look at the laptop screen IRL everything is very small) But in the headset it functions almost as though it was nearly a 50" 4k TV. So presumably has the macOS text issues but worth it otherwise.
And the mouse latency is fine wirelessly?
(Sorry, I don't love the retina word but I haven't found a substitute since high DPI resolves to so many other things.)
Exactly, tiny text on the main screen (if I un-dim it, Immersed dims it automatically). I am not aware of text issues, I guess I never noticed any.
There is a mouse emulation mode that is supposed to be more responsive, and native mouse - I use the native setup and don't notice any lag. Just have a good router and be close to it.
Retina is the only word I know :) because it started way back on iOS/iPhone before it was that common. And probably because I use a Mac.
One other thing that is an unexpected bonus. It rains where I live. A lot. And when it is grey and dim, I can sit in a "sunny office". In fact, I even tweak my day to the virtual environments. Sunrise in a mountain lodge in the mornings, sunny office or ski chalet in the afternoons. Very positively mood altering.
If I could afford a Porsche I would still get a manual option. Changing gears cleanly, heel-toe blipping the throttle when gearing down, getting the right gear at the right time - simple pleasures. It seems the more refined cars become the less character they have. Even the equivalent cars to my old dependable friend feel like lesser cars. Annoy CVTs, electric power steering, and finishes that feel cheap. And windows - I have nice big windows where I can see everywhere.
Dual clutch in more expensive (fast) Porsche's are a lot more fun bc you have less to worry/freak out about going at speed (I'm not that good of a driver...).
In cheap Porsches like the Boxster the manual is a ton more fun, since those cars don't really go very fast, so you feel more engaged. But Porsche manuals are kind of janky and notchy in those.
Maybe I'm just reminiscing "good ole times" but the manual in my S2000 was and is still the best manual I've ever driven.
You will be inside of Xcode for most of your time - I just upgraded to a 13" Air (maxed out configuration) from my 2012 11" Macbook Air which was still fine with Xcode. I think any Mac will run Xcode well enough.
When last did you change jobs? A year ago I did and set a hard minimum at 120, and managed 2 offers as high as 160 and took a lower one due to more interesting work and great environment. And had to cancel 3 more on site interviews that knew my range was 130-140.
My previous job had a 2% raise over 3 years, with a salary out of touch with the current ranges.
It seems the only way to get a raise much of the time is new work (and practice negotiating!)
Just a few months ago. What's your specific discipline and exp? It's good to hear that there's a lot of room to grow. I'm well aware of when/how the biggest gains are made, but I appreciate the insight nonetheless. I consider 110k at the moment to be pretty ok, just considering my extremely spotty track record atm. I'll stick around for now to rebuild my savings and get some current exp, but won't sit on it for too long especially if the compensation doesn't seem right.
The IDE is where the super powers are. Like any IDE it just takes a little time. https://pharo.org/ has an online course to get into it.
Being in a live system is unlike anything else - the first time a debugger appears and you fix the bug in the debugger and just hit the “continue running” button is a rush. TDD inside the debugger is amazing. And do much more.
You really need to experience it, else it just sounds like hot reloading features of current tech.
Being that other languages are Turing-complete ...
Which doesn't really mean much when it comes to the standard developer experience and how that differs between programming a live image and the tooling built around that versus manipulating text and the tooling built around that. One lives at the abstraction level of running code and the other at the level of syntax.
In C/C++, I can do live debugging, reverse-time debugging, edit-and-continue debugging, multi-device debugging, multi-threading debugging... We also got language servers, on the fly retesting and recompiling, all kinds of profiling... All that with free or open tools readily available, not to mention paid, proprietary ones.
In higher-level languages, fancy features are even more prevalent.
They are still positional in Swift. color(r: 255, g: 255, b: 255) is not the same as color(b: 255, g: 255, r: 255). Also the parameter names are part of the method signature.
Is 10 years normal for the lifespan of a car? Mine is 23 now, still works fine, and I feel is nicer than similar new cars in terms of interior finishes, hydraulic power steering, actual buttons for climate control that do their one thing well.
I don't drive much, but then I don't remember any childhood cars of my parents being at end of life at 10 years, and those were used in daily commutes.
Do the batteries decay over time? If a Leaf only has say 8k miles a year, will the batteries simply fail to hold charge after 22 years?
It's common for a major component to break after 10-12 years and its repair costs exceed the resale value of the vehicle. On my last car, it was the AC compressor. OTOH, some models like the 90s Toyota Camry seem to last forever.
Something that has always bothered me is "resale value" of a car. I have a car with ~215000 miles, and its "resale" value is $1.5k. However, I gladly paid for $500 for a minor repair on it (I had to replace a rim due to hitting a curb), even if it was supposedly a third of the value of the car. Even when/if the engine/transmission goes out, I've considered rebuilding or replacing it, because I see little reason to pay so much more for a new car when the current one is in such good condition.
As you experienced, spending $500 to keep a $1500 car from becoming a brick is a great value.
If/when I have the time, my plan is to take cars like this and part them out. Lots of people out there willing to pay for a working OEM part to de-Brick their car.
If you’re patient enough; selling rims one by one would pay off. Nobody really wants to replace all 4 when they really needed one.
Yeah it was, I bought a more expensive car when I was younger. When this one gives out I'm getting a cheaper one (hopefully without phone home electronics too).
Your car won't last forever. You will need to buy another car sometime. Money you spend on repairing your current car could be put toward purchasing the next one.
Let's say a transmission replacement costs $1000 for your car (that's low, by the way). You could sell your car now for $1500 and buy a another one, or you can spend $1000 keeping it on the road for a few more years, sell it for less than it is worth now, and then buy another one. That $1000 was wasted since you had to buy another car anyway -- you would have saved that $1000 if you bought the replacement car sooner.
How are you getting $1500 for a car that needs $1000 worth of transmission work?
That only works if you can see into the future and know that you will need transmission work soon, and then it requires you to find a buyer who doesn't share that opinion. Essentially, you have to screw someone over.
Otherwise, if the transmission is already broken, the situation is that you either pay $1000 and get a working car (ie. repair the transmission) or sell your car for $500 and then buy a new one.
I agree, but going back to your analogy, I would rather spend the $1000 and not have a car payment for another few years (assuming a $200 for a year, that's $2400 I'm not paying).
My bigger worry is if I get into an accident, the value of the car is so low that the insurance will total it, and now I'm stuck with buying a new car.
Both car parts and battery longevity depend on how you use them more than how long — so those statements are about overall statics; there will always be anecdotes.
This likely means that a majority of Leaf cars will need repairs that cost more than the car is worth on the market, while the battery still has value, although likely not in a new car as they will be worn out a bit and technology will have ten years to improve by then. Elon Musk has already said that Telsa is planning on re-using batteries from Telsa cars into on-grid batteries, where weight is less of an issue, so partial batteries are fine. That’s likely what will happen to Leaf batteries in 10 years too.
Road salt and Ocean Air destroys car bodies. The drivetrain can be fine, but the body just falls apart around it.
There's going to be an interesting time for Used Cars coming up, with all the electronics and complex parts. Where cars could be worked on in your garage or local shop, now need a trip to a dealer to work out the Electronic Wizardry.
Followed by the dying out of non-diesel ICE shops turning into just Brake and Tire places.
I've had good luck avoiding body rust in Minnesota, but on my last car (sold at 15yrs old) I ended up replacing every suspension and brake component over the last 3 years due to corrosion. My current car is 10 years old and I've already replaced a couple seized calipers.
I have a 2007 Saab and even the dealership can't sort out the ghosts in the electronic wizardry. Not at any remotely reasonable cost. It's basically deal with it or spend thousands of dollars replacing at least the main computer, which has assumed far too many functions. The variety of things that malfunction together is absurd, and slightly frightening. I can't trust that an issue with the door locks or climate controls isn't going to manifest as the engine turning off or the steering column lock engaging mid-drive.
I find it a funny thought because, in my experience, the OBD port often tells you exactly what is wrong, or at least where to look.
And if you have a common car (like my parents’ Corolla), an ambiguous code can tell a lot when you check the internet and you get directed to the most common failure mode.
Trying to look up statistics on this, and what I find is very strange:
Both in Europe and in the US, average age of vehicles on the road is given as ~ 11 years, while average age at scrappage is given as ~ 15 years.
How do you even make an age distribution that agrees with those numbers? How do you make those numbers agree with the statistics of vehicles sold per year, which is relatively steady?
A few ways when you use averages and only use one type of average - mean average without including mode or median average types.
The age of on the road vehicles can be skewed by new cars.
The age of scrappage can equally be skewed by a few new cars written off and as such, scrapped.
Then we do not know average time of the road, the transition time of sitting in a garage/off-road and then scrapped a few years later. That could be a short period or decades. That again would skew averages.
As you can see - I have a pet hate about averages when they just use the mean average. Without knowing the other two averages or complete access to the data-sets - a biased perspective can and will be the outcome more often than not.
It's like a company employing 100 people - 99 earn 10k a year and one earns 1 million a year. The company can and often will say that their employees earn on average 19.9k a year. When the median and mode forms of averages would both in this instance yield an answer of 10k.
I'd be most happy if any use of averages has to include all 3 forms of averages - after all, we do teach them in school's, let's use them and save so much confusion, bias and statistical abuse.
I like your thinking. I've always thought mean, median and mode should be thought of as different possible "average" definitions. But common usage always seems to have average == mean, and the other two as slightly less important ideas. This Wikipedia article pleasingly implies my (and your) preferred model is actually the correct one.
If it grows faster than sales, fewer cars must be taken of the road.
Could be as simple as households holding on to cars longer because they cannot afford to replace them, because modern cars last longer, or because they can afford to have a second/third car in the garage, but not a new one.
It might seem like the average age should be 7.5 years but cars that last longer than 15 years will contribute more to the sample than the average car, thus giving an average of 11.
Think about any product using rechargeable batteries that you have ever owned, and you'll get the idea. There will be a gradual reduction in range until the batteries really need to be replaced.
“Stepping through code a line at a time” is a rather narrow definition of using a debugger. Setting a logging breakpoint. Conditionally breaking. Introspection by calling functions while the program is paused. Testing assumptions by calling functions. Conditionally pausing the program. Setting a breakpoint in code and then calling functions to activate the code path to the breakpoint. This is the core of what lldb does for me. I agree, single stepping is rare and is like looking for the needle in the haystack. But are all these other aspects not assumed to be using the debugger?
That says that the majority of soy meal goes to animal feed. I couldn't actually get the amount of soy beans used for animal feed. Perhaps you can find it.
According to this [1], they were forecasting about 4,200 million bushels of soybeans being harvested in 2016 with nearly 2,000 million bushels being exported (about 47 percent according to the source).
I tried to find a reputable source for soy bean use in the US and failed, but some sources I was able to find (mostly vegan activist groups) stated that 80% of soy bean use is for meal while 20% is for oil. Of the 80% used for meal, 97-98% is used for animal feed while 2-3% is used for food.
As far as I can tell that means that if we round things up to the nearest 10%, about half of the soybeans grown are exported, 40% is used for animal feed (cattle, chickens and pigs) 10% for oil (of which some is cooking oil) and a negligible amount used directly for human consumption.
Possible the parent was considering only cattle consumption because another source I found suggested that you don't want to feed cattle more than 15-25% of their diet on soy because they can't digest it. Chickens and pigs presumably don't have the same problem.
I find it interesting that in truth the largest category of "use" for soybeans in the US is as an export trade good. I wasn't actually following the discussion above closely so I'm not sure how it impacts anything. However, it occurs to me that possibly the land could be put to better use. However it was also interesting to me that according to your source Wisconsin has 11K soybean growers over 1.6 million acres. That's an average farm size of 145 acres. As a person who grew up in the prairies of Canada but now lives in Japan, that seems to me to be both not so big and also gigantic :-) (I don't think I've ever seen a Japanese farm bigger than about 30 acres!)
