This is the primary reason the Minibook X won out in my searches: It's the only small device that has a keyboard layout that puts all of the keys in the right spots.
They're sometimes an odd size, but when I hit the wrong key due to a sizing constraint, I don't even have to think: Backspace, hit the right key with mildly adjusted positioning.
I've tried a few machines with different layouts, and that's never the case - and having to stop and look at the keyboard to find a key interrupts flow in the worst kind of way.
I have this laptop, and it is amongst the best laptops I have ever owned, despite being awful in many ways. It has almost completely replaced my use of my M4 Macbook Pro, simply because I always have it with me. That, and it can run Linux.
I don't share the complaints of the OP about the keyboard or the screen, though. The keyboard is fine, I can hit about 110WPM on it, slower than my regular pace, but enough that there's no dramas. The layout is great: Occasionally there's keys that are too small (looking at you, apostrophe) but everything is at least in the right spot, which is way more important.
The 2K display at 10" is high enough DPI that everything is totally crisp, and you can unlock ~95Hz (bad for video, good for everything else) with a bit of a tweak. You can also smash a byte into the EC at the correct offset and access the full unrestricted BIOS -- mostly to crank the RAM up to 4800MT/s.
I'm running vanilla Arch with Niri and Noctalia, and it's a dream. It's my primary dev machine, used in combination with a remote server with a tonne more grunt. If it broke tomorrow, I'd buy another - and I wouldn't do that with my macbook.
I agree. The keyboard is fantastic, it is the best smallest keyboard I've ever used. Debian 13 works out of the box and there are no screen rotation issues.
The cause is just that the panel is mounted rotated on the device. It's supposed to be used in a tablet where the top is the short end and the side is the long end, opposite to a laptop.
> Yes, but no room is made for people who see no use for it. There is a forced-consensus that this technology is useful, which I have to combat against at work.
This is the crux of the issue -- The technology is useful. Using it appropriately is probably the thing that people are ignoring, but you're conflating one and the other in your comment.
It is not useful to you in this case, and complain that it is an overall detriment in your industry. Those are fine and reasonable statements and conditions, and I see no reason to disagree with them... But your first statement, people who see no use for it? That is, to me, as off-putting an opinion as the consequence-unaware hypebeasts who are running OpenClaw with access to their trading accounts and can't see why others aren't.
I sympathise with the idea that everyone wants to use the new hammer and so is treating every problem like a nail, but hammers are still pretty good tools. (And you can ignore the ex-NFT-fans hammering on their dicks in the corner.)
I mean only that I see no use for it myself, in my own work. I'm sure there are people working in roles around me who believe they get some use out of AI doing their work for them, and they will have to answer to auditors when they find problems with their work, or when someone is killed.
To me, as a non-techie person, it feels as if people who work in software believe that because their work can be done by AI, everyone else's can, too. Or that this would be better, simply because it proposes a technological solution to human work — it is taken as read that a solution which uses cool sounding computers and data farms is better than one done by humans with a pen and a pad and life experience. They don't have to justify this belief, because the money is on their side.
I don't mean to tar you with a too-wide brush, and I feel like you have a good handle on your personal acceptance for LLM assistance. No complaint there.
I do think, maybe alternative to your view, that LLMs can provide useful feedback to graduate-level employees in most fields.
It is not that the work can be done by LLMs -- we're not there, yet, in software or otherwise -- but that LLMs as useful tutors specifically in regard to denouncing known bad ideas is largely applicable all over.
What I mean by the above is that I have yet to find a truly interesting idea spun from whole cloth by an LLM. They're mediocre at it. They're trained from the aggregate thoughts of those in every industry, and you and I both know that the aggregate of the industry is, generally, mediocre.
Conversely, though, is the hit: They won't be worse than mediocre. An indefatigable tutor who gives no great advice but will counsel you against blowing yourself up (or cutting a limb off with a rope, or falling overboard) is, to me, worth an amount.
The failure modes will get better, the advice will get better. Are we there, now? Unsure. You can tell us all better.
What does that really mean though — ten more years of data centers exploiting local communities for their resources will mean that a computer might be able to teach people to tie knots, and reliably check their work... No government would allow that to certify someone, and no company would risk the lawsuit when someone dies doing what the AI tells them, so it's a non-starter. Even if it were possible, and governments got on board with certifying training like that, would anyone think this was better than what we have now?
What are the likely use cases in my industry then? That AI is used to bodge the important paperwork that protects lives; is used to draft legislation; is used by both employees and management to do things like personal development reports.
Is anyone meant to be impressed? Is this worth communities having their water stolen from them?
I appreciate I am skeptical, but it is hard not to be when the world spends all day telling you a piece of technology is going to fundamentally change the world, and in real life you only see people use it to blag CVs, personal reports, and lesson planning.
> "What does that really mean though — ten more years of data centers exploiting local communities for their resources"
That is purest hyperbole. Data centers use a lot of electricity, but they are hardly looting local communities. The water issue is wildly exaggerated, unless a data center is located in a desert, because most water is recirculated.
And why do you think no one will allow an AI to certify someone on certain topics. Their knowledge at the moment is roughly the average of people in the field. Is an average person in your field not able to certify others? In any case, AIs are improving very rapidly, so what is not possible today will be possible tomorrow.
As an example, let me point out the Tesla FSD. On a per-mile basis, self-driving Teslas have a massively lower accident rate (less than 20%) than human-driven vehicles. That is a very physical activity being handled by an AI.
That’s also an algorithm. An unsophisticated one, but an algorithm nonetheless.
You can (and should) argue that such a simple algorithm doesn’t “count”, but fundamentally the exact wording of the grandparent post never works, legislatively.
> That’s also an algorithm. An unsophisticated one, but an algorithm nonetheless.
The problem always has been "(personalized) opaque algorithms". Time sorted by followers isn't really opaque, nor is "sorted by likes" or whatever. The problem is always pulling in parameters that a users either has no active control over or are so variable they effectively could be random.
Can everyone just please stop saying "well ackshually sorting is done with an algorithm" and just assume at least not-idiotic-intent here? No no one will ban "algorithms" or suggests anything of that kind. Yes it's a terrible name. Yes it will be hard to formulate what's allowed and what isn't. But a very simple litmus test is: what are the inputs to the algorithm?
users coarse geographic location? Fine
AI detected language of the content? Fine
global popularity of the video clip? fine
user's past behavior: number of videos with similar content they watched? Average number of seconds this particular user usually waits until scrolling further?
The pattern is obvious. Personalized algorithms is what's targeted. Let's keep the discussion intelligent.
Your litmus test isn't correct and your assumption of personalisation isn't correct either. All of the criteria that you see as fine are controlled under the relevant legislation and are considered personalisation, requiring transparency etc.
Furthermore, bills have been brought to EU parliaments that have erroneously attempted to ban all forms of ranking, which would include even the most basic information retrieval algorithms. So it isn't obvious at all what is meant by 'algorithm'.
If you're referring to gpt-2 in 2019, that primarily about concerns with it being used by spammers and fake content generators. In retrospect, that was a totally valid concern.
They had a reddit with GPT2 back and forth I have to say I got suckered into a conversation before I figured it out -- it was definitely the OG Moltbook of non sequiturs
I dug a little into this because I was curious who was more correct here.
From wikipedia, which links to what seems like a relatively reliable source:
> The Singapore Department of Statistics broadly defines "Chinese" as a "race" or "ethnic group", in conjunction with "Malay, Indian and Others" under the CMIO model.[10] They consist of "persons of Chinese origin" such as the Hokkiens, Teochews, Hainanese, Cantonese, Hakka, Henghuas, Hokchias/Foochows, Shanghainese and Northern Chinese, etc."[11]
So I would, on the balance of things, think that kccqzy meant what they said, and was pretty correct about it.
Group Policy and Active Directory are dead, for all intents and purposes.
It's now Intune (via OMA-DM), and Entra. Both of those products are about as bad as you might imagine the "cloud" versions of GP & AD might be.
They are better, in ways -- no longer having to care and feed for domain controllers is nice, and there's no longer an overhead for additive policy processing, so endpoints only get a single set of policy and log on much quicker -- but for the most part, enterprise management of Windows devices is in a worse place than it was ten years ago.
Try to figure out how long it will take an online Intune device to discover a new policy: As far as I can tell the answer is "eventually". There are bandaids for this, because of how infuriating it is, of course, but all time guarantees are basically gone.
Ask me a decade ago what an enterprise should do, and my answer would be straightforward: AD, GPO, Exchange.
> Ask me a decade ago what an enterprise should do, and my answer would be straightforward: AD, GPO, Exchange.
That was also the answer two decades ago. But if AD and GPO are now dead, what killed them and what are the options? Is the problem mobile and BYOD?
I’ve been primarily on Macs since that time where endpoint management isn’t much, so there are fewer knobs to fiddle with. In some ways it’s nice in that admins can’t screw around too much with my system. In other ways, I’m sure Macs feel limiting for those in charge of enterprise security. However, most endpoint management feels like it’s written for Windows with Macs as an afterthought for checklist security. Knowing that, I’m happy there are fewer places for dodgy software to be able to interface with the OS.
> "if AD and GPO are now dead, what killed them and what are the options?"
The changing world. AD and GPO come from the mid 1990s before pervasive internet, before WiFi, before Cloud computing, before people had multiple computers, before iPhones, before AWS cloud infrastructure, before Kubernetes, before cheap fast hardware for virtualization, before cheap bulk storage, before BYOD and WFH and everything-as-web-app. Before that was the world of isolated 8-bit machines, expensive Solaris workstations and Unix mainframes with expensive admins, and after say 1998 the world was cheap Compaq/HP/IBM hardware running Windows server and Windows 9x desktop, and after about 2003 it was Windows Small Business Server (AD, GPO, SQL, Exchange, SharePoint) and XP Pro desktops.
Cracks started showing when people wanted to logon to a laptop away from the office when it couldn't refresh policies, run logon scripts, talk to domain controllers; when people wanted 'offline files' from a company file share while away from the office, but wanted their corporate email to work when their laptop was online but not pull down company settings over a dialup modem. More cracks when they got a Blackberry or iPhone, more when AppStores appeared and people expect to be able to install whatever they like, more with the rise of Apple Macbooks, with the growth of website based services people can use from anywhere, more with Amazon AWS where company infrastructure is on someone else's premises, more with BYOD and WFH, more with people expecting software to be cost-free, being trivially able to spin up Linux web and database servers because there was plenty of CPU/RAM/Disk and no worries about licensing costs.
> "it’s nice in that admins can’t screw around too much with my system"
If it's a company device, it isn't your system. The company has legal oblications and practical concerns that conflict with your desires as an individual. That might be pushing full-disk encryption or updates, or auto-locking, or restricting use of USB or websites to block potential customer information leak points, or trying to stop you saving work locally that might be lost if the device fails, or trying to stop your device being an entry point for malware or ransomware, or trying to stop you screwing around with their system which costs them employee time to fix and your downtime while it's broken.
It was absolutely not the case two decades ago.
There were no other options for an enterprise fleet, 20 years ago, if the question was asked. If you weren't Google (who never asked the question anyway), the answer for managing 25,000 endpoints was to use Windows devices with Active Directory as the management plane. Anyone doing anything else was in for a world of hurt... and that's why every enterprise ended up on Windows, and why everyone targeting enterprise management targeted Windows -- because that's what the endpoints were already running.
What killed AD & GPO was Microsoft, in their bullheaded push toward Azure everything. Instead of listening to what it was that the enterprise customers actually wanted, they designed a system that made sense to them, but to no one else. The original UI was written in Silverlight. It was horrific.
No, I meant that Windows AD was still the answer two decades ago. I can see how that may not have been clear - I edited my post to include the quote I was replying to. (You said one decade and I was just extending that timeline back another 10 years.)
There was LDAP and Kerberos support for *nix management, but nothing you’d deploy over a thousand end devices.
And you’re right, it wasn’t a question that got asked, because there wasn’t ever a second choice - AD was the only option.
I remember it almost being a trope at the time that every Kerberos question thread eventually landed on some subtle / niche incompatibility or edge case.
No alternative, you can't realistically fully control everything everyone does on every device in their possession. It was job security for useless control freaks, the products never should have existed.
I absolutely have, which is how I know what I said is true. I know who gets blamed in that scenario too. The point of that job is to be the scapegoat when things go horribly wrong. And they will, because you can't realistically ever control a device in someone else's possession. The application level is where all expectations of control and liability should end.
As someone heavily involved in the hospitality (read: beer) area, this doesn't really line up with reality in Australia: there's only one state (South Australia) that doesn't agree on the major standard sizes: Pints are 470ml, schooners are 425ml, a half pint is 285ml, and a pony is 140ml.
There's colloquialisms for a half: pot, or middy, mostly. Hobart will call a half pint a ten, because it's 10oz, but they also know what you're talking about when you ask for a pot or a half pint.
Then there's South Australia, which will serve you a pint at 425ml, a schooner at 285ml, no one there outside of specialty craft beer bars have any idea what a half pint is, and if you want a proper pint you need to ask for an imperial pint. I have never seen an 'imperial pint' advertised in Hobart - it's just called a pint there.
Source: I have pretty extensive drinking experience in pretty much all of the Australian capital cities, except Perth.
> there's only one state (South Australia) that doesn't agree on the major standard sizes: Pints are 470ml, schooners are 425ml, a half pint is 285ml, and a pony is 140ml.
> Source: I have pretty extensive drinking experience in pretty much all of the Australian capital cities, except Perth.
I don't drink as much as I used to so this might be a little outdated, but in Perth "Pints" are 570ml. It was rare, but becoming less so, for some places to serve you a 470ml schooner when you ordered a pint. We avoided those places.
...Embarrassingly, I have typo'd in my original post, and it's too late to edit. Pints are 570ml (not 470ml) everywhere on the East coast - hence why a half pint in Tassie is often called a ten - because it's 10oz, or half a 20oz/568ml pint.
Maybe not today, but in the summer of 1990 every pub I went to seemed to have a different glass and I was somehow expected to know what they were called...
I was decidedly not old enough to drink in 1990 and culture in general in Australia was much less homogeneous back then, so you're probably right for the times.
They're sometimes an odd size, but when I hit the wrong key due to a sizing constraint, I don't even have to think: Backspace, hit the right key with mildly adjusted positioning.
I've tried a few machines with different layouts, and that's never the case - and having to stop and look at the keyboard to find a key interrupts flow in the worst kind of way.
reply