I wish they would make big displays again. Like 32” big 6K.
24” or even 27” feels like such a downgrade.
Also please make the iMacs usable as external monitors agains. Would buy one as a “livingroom computer” instantly if it was also possible to occasionally use it as a docking station for an air..
I've been using a new program called RetinaRelay[0] to use my 5k iMac as a second display for my M1 Macbook using an ethernet (or Thunderbolt for even better performance). Works brilliantly. It's definitely higher latency than a normal monitor (my ethernet connection is 45ms vs 5ms for a monitor) but it's not noticeable for coding and miles better than remote desktop or similar.
I'm pretty sure it relies on Mac APIs like Metal and ScreenCaptureKit but it's worth reaching out to the developer. He was very responsive when I requested features, and it may be a lot easier to build a windows application that adheres to the protocol using agentic development.
Thank you. I have been looking for something like this for a long time. My 27” 2015 iMac is getting very long in the tooth, but that 5k screen is still beyond beautiful.
I’m still angry that they deprecated target display mode. For a company that talks so much about recycling it’s really messed up they don’t support it. Such an amazing way to give life to old but incredible monitors - you’d have to spend $1000+ to get anything remotely resembling the quality of that display. You can’t even use ones that previously supported it on current Mac’s.
There are countless non-5k iMacs. I never said it had to be that. I had a beautiful 27” 2.5k display from 2011 I could’ve put to work.
There is no excuse other than laziness IMO. They likely decided not enough people use it and that they didn’t need to keep an excellent feature (total speculation to be fair). I can use iMovie to directly control/run playback from a dvcam from 2002 via like 4 daisy chained cables - including FireWire 400 - but they can’t connect an iMac anymore over thunderbolt 4 after supporting that for over a decade? Nah. Maybe there is a legitimate reason but I am incredibly skeptical.
Yes the previous iMacs sent a signal. Their current computers don’t receive the signal. This is not about the 5K display, you’re missing the core problem. It stopped working when the silicon line came out. You can’t get any iMac to work in target display mode on silicon Macs.
That’s not a technical limitation, that’s laziness. Go read more about this. It simply doesn’t work anymore without 3rd party solutions.
You cannot grab an iMac, plug it into a silicon Mac, and get a picture on the iMac (without 3rd party software). This is incorrect. Please go look this up. The feature stopped working when silicon Mac’s came out. It only works on Intel Macs. 5K iMac or not.
Target display mode, the feature that allowed this, is no longer supported.
I have already explained that and it’s not the same as native support any more than display link means one can claim M1’s run 2 external monitors (Mac mini excluded). I wrote this multiple comments ago:
> It simply doesn’t work anymore without 3rd party solutions.
When 5K iMacs first came out in 2014, they were mostly limited to displayport 1.2, which was unable to support 5K without either dropping to 45Hz or using chroma subsampling. So the 2014 version is excused, and we can excuse the 2015 version too.
But with the 2017 revision, they had a displayport 1.4 GPU in there, and there was no good reason for leaving display target mode out.
And they've left it out ever since.
Streaming compressed video with a significant latency penalty doesn't count. But if it we act like it does count, then they lose their excuse for removing target display in the first place, because even in 2014 it was possible to do 4:2:0 5K @ 60Hz over a normal connector. That looks better than compressed video does!
Absolutely. The display on the iMac 5K was amazing. Ended up giving that machine to a nephew of mine when I moved to Apple Silicon but Apple really dropped the ball here.
I think you will find that 4K is generally sufficient at 32". Text is sharp enough, and a high refresh rate is probably more important at that point. There is also the issue that not even a 5090 can push enough fps at resolutions higher than 4K in demanding games.
I have 4K at 32". It's pretty sharp but at 6K the pixels would be significantly less visible, and I could run it at an even 200% so that older programs don't have scaling issues.
Good point, I am looking forward to the day OLED 6K is common. A higher resolution is always better after all. At the moment however I think 32" 4K is pretty much the sweet spot for a single monitor setup however. It's a decent pixel density and high refresh rate panels are avaible.
You need to increase UI scaling, not turn down the resolution. All modern desktops support this in some form. I would only lower the resolution if the GPU can't keep up in games after exhausting all other options such as AI upscaling.
I guess you guys on Mac don't play games. There is no GPU that can provide a consistently good framerate at 5K in a recent game. And that Mac monitor is probably 60Hz, so it's not a clear win over 120Hz+ at a somewhat lower resolution.
I feel like I have to remind people of this quite often, but the history is such that npm was lightweight at one point, bundling wasn't a thing, and while `isodd`/`iseven` are of course silly, things like `isarray` were not functions that existed back then (we didn't have Array.isArray). `typeof [] === 'object'` in JS, so e.g. my package `is-arrayish` checked for a similar structure to an array (whereas Id guess `isarray` checked for the prototype). `isarray` failed for the `arguments` keyword, which was needed for variadics before argument spreads were added to the language I believe in ES5.
So of course they don't make sense now. But they were created for a reason. Before even Markov chains were a fad - let alone LLMs - we were trying to be as efficient as possible and maximize code reuse I stead of writing the same helper functions over and over again. That's what you're seeing.
Additional Context: for about two years functional programming was REALLY popular in the Node community. It was a fad to chain tons of tiny functions together, and thus lots of people wrote tons of tiny functions. This is why lodash/fp exists.
Yes and the critical issue was tree shaking. Nowadays we have tree shaking so it doesn't matter as much but in the past people preferred small single function packages because they had less impact on the download size.
> Ut oh, your code is now broken because isOdd(2^55+1) returns true now...
I think you messed up this example. Whether I literally use "2^55" with XOR or replace it with "2*55", that version of isOdd returns false.
False for isOdd(58) is obviously correct. (Also thanks C for permanently screwing up the precedence of bitwise operations because you didn't want to break some existing programs in 1972.)
False for isOdd(36028797018963970) is also correct, and if you expected to send in a different number the bug is in the "+1" not the isOdd.
But there's no bug in isOdd. You're sending the number 36028797018963970 into it, which is clearly even.
Putting extra code between the parentheses of the function call doesn't make it the function's responsibility. As nice as it would be for debugging if you could stuff your entire program inside of isNaN((function(){ /* your code here */ })()) and force your browser vendor to fix all problems.
Despite what most JavaScript implementations will tell you, 2 to the 55th power is 36028797018963968, and adding one to that value is 36028797018963969. That's clearly odd.
There is no extra code between the parens. I just put them there so there wouldn't be any question as to operator precedence. I do see now that hn ate my double star, but I think you know what I mean since you told me the value that is spits out when you do the exponentiation
You have a plus and an exponentiation in there. That's code.
var n = 2**55 + 1
console.log(n)
isOdd(n)
n is 36028797018963970. isOdd(n) is giving you the right answer. Putting the +1 inside the parentheses and talking about calculators is a sleight of hand that lets you pretend isOdd gets an odd number, but it doesn't. No odd numbers are around by the time isOdd actually does anything.
The problems are in + and/or our expectations of +. It does not output 36028797018963969, and we must acknowledge that.
I don’t think it ever made sense. Code reuse improves efficiency when the code can be shared in memory, or when it needs to be updated and you only have to change it in one place. JS packages don’t give you sharing beyond what you’d get from copying the code. And these little things don’t need to be updated, and in fact you probably don’t want them to be.
It’s a case of doing something without understanding why it’s done. Packages are good, code sharing is good, so use it for everything. But it misses why they’re good.
I was definitely saying it at the time. But I wasn't embedded in the ecosystem, it was very much "those JavaScript guys are nuts, why would they do this?"
There’s a bit more nuance as to why. It’s not fair to say that the average JS dev is reaching for a package like is-odd/is-even.
Years ago when npm was just getting started there was a lot of experimentation and land grabbing for packages. A few “prolific” developers were pushing these tiny utilities and then using them in their own projects which ended up being required as deps in other projects and then snowballed into is-odd being included in webpack at some point (I think I have that timeline roughly correct).
It’s still a crappy problem for sure but it’s not fair to paint most JS devs with a brush so broad.
Everything that touches JavaScript in the corporate world feels broken.
Look at any full stack job post. It’s a mess of tech stack nonsense on the backend for people who are terrified of JavaScript and a layering of framework madness on the frontend for people who are still terrified of JavaScript. So it should be no surprise to see packages like those in common use when people aren’t really writing, or even reading, the real code anyways.
That is just the coding aspect of it. There are many additional challenges to working with a bunch of cowards whose primary job is to pretend to be something they clearly aren’t.
There’s not much evidence these are being used, only that they are dependencies for something else; that’s why the download numbers are so high.
I wouldn’t say it’s broken, I’d say there are tradeoffs, and devs have known this and discussed it since the start of npm or any package manager. You automatically get some bloat when you use other people’s software. That’s the downside. The upside is you don’t have to write the code yourself and you can create things more quickly by not solving problems that others have already solved.
It’s worth noting that AI has some of the same tradeoffs. The quality of what you get is still proportional to your prompting & reviewing effort, and spending low amounts of effort often results in similar amount of bloat.
The real underlying issue is the economic pressure - much worse in East Germany than in West Germany. People have problems, but the real problems are not immigration or green politics.
What the numbers say is that Germany is deindustrializing. It's not just the car industry, it's a problem in pretty much every sector. It's not what I say, it's what the numbers are saying. https://www.reuters.com/business/german-industrial-output-fa...
I'll introduce subscriptions soon, we're currently still in invite-only beta, but the subscriptions will be very much like GitHub/GitLabs with individual and team pricing.
motan | Software Developer C#/.NET (4 openings) | Isny im Allgäu, Germany | ONSITE (partial home office) | Full-time | NO VISA (EU work authorisation required)
motan builds the equipment that feeds plastics processing - drying, mixing and conveying material into injection molding and extrusion machines. Our equipment runs in manufacturing worldwide.
(don't care about the touchscreen)