How's the battery life? Can you replace the battery if/when it gets old?
That looks like something I could buy. I've really wanted a tiny console PC with RS232 and ethernet for a long time now. I thought about building one into a custom keyboard using something like a raspberry pi but I haven't had the time to follow through. This thing looks like it could make my diy project unnecessary.
I also haven't found phones particularly appealing.. mine gets 5-6 days on a charge because it's mostly just an alarm clock. Any time I try to do anything with it, I get frustrated by how clumsy it is compared to an actual computer. I do like being able to look at maps or make a call in an emergency, and it's handy having a camera always in the pocket, but that's pretty much where the appeal ends.
There's also some low-hanging fruit if someone wants to contribute. E.g. the developer docs are rather outdated. I recently implemented AMD FSR as a Gimp plugin but all the docs led to code that resulted in a slew of deprecation warnings. Also poor performance and some thing just not working right at all (tile cache). I kinda got frustrated with it and dropped the gimp parts altogether, but if I had more time, it shouldn't be hard to figure out and maybe improve the docs or write an up to date tutorial.
> If we want top-grade products to remain available without a direct monetary transaction
Fantasy world. These products do not exist, as far as I'm aware. The reality is trash products. I couldn't care less if all that trash just vanishes from the internet.
I trust Google to randomly lock me out because their stupid AI determined that I'm a suspicious geek instead of a normal person. It's happened before, it will happen again.
> You could say a human is laundering GPL code if they learned programming from looking at Github repositories.
I don't have photographic memory, so I largely don't memorize code. I learn general techniques, and memorize simple facts such as APIs. I can memorize some short snippets of code, but these probably aren't enough to be copyrightable anyway.
> The type of model they use isn't retrieving
How do we know? It think it's very likely that it is largely just retrieving code that it memoized, and doing minor adjustment to make the retrieved pieces fit the context. That wouldn't differ much from finding code that matches the problem (whether on SO or Github), copy pasting the interesting bits, and fixing it until it satisfies the constraints of the surrounding code. It's impressive that AI can do that, but it doesn't sound like it's producing code.
I think the alternative to retrieving would actually require a higher level understanding of the world, and the ability to reason from first principles; that would be much closer to AGI.
For example, if I want to implement a linked list, I'm not going to retrieve an implementation from memory (although given that linked lists are so simple, I probably could). I know what a linked list is and how it works, and therefore I can produce working code from scratch.. for any programming language, even ones for which no prior implementations exist. I doubt co-pilot has anything remotely as advanced as this ability. No, it fully reliant on just retrieving and reshaping a pieces of memoized code; it needs a large corpus of code to memoize before it can do anything at all.
I don't need a large corpus of examples to copy, because I use my ability to reason in conjunction with some memoized general techniques and common APIs in order to produce original code.
I'm with you on this. The system is blatantly broken, and one way to get something done about it is to get everyone to abuse the hell out of it so that the system gets removed or fixed.
APL's usage of monad predates its use in conjunction with modern functional programming languages, by the way. It goes back to the 60s, and there are plenty of books and papers where these terms are used that way.
I can't say I care too much which terms people use, but in context of APL, I prefer the terms that were used by Iverson and have been in print for more than half a century.
Is it really or is it just in the SV bubble? Or is this a case of "it's not interesting if it's not in SV"?
Sometimes reading HN gives me the feeling that there is no "tech" other than FAANG in the US. Or somehow every little "tech" company is just making FU money, which sounds hard to believe.
But stack languages generally do evaluate left to right.
I don't see why you couldn't do right to left. Makes no semantic difference.
But the original post has a snippet that should not only be evaluated right to left, but also bottom to top. Unless their indentation implies hidden parens.
> I think I’ve heard that the APL semantics is commonly described right to left so might be related?
Not particularly related. It's just that every function is either monadic (operand on the right) or dyadic (infix). That makes it a case of not needing to explicitly specify where the function arguments start and end, still without using a stack; it is purely syntactic, and obvious (although you do need context to parse anything that uses user-defined things). Parentheses are still needed for the left operand of a dyadic function if it is to take an expression more complicated than a plain array.
If you had functions of higher arity, then it would become necessary to add parens, delimiters, or a stack.
I'd be interested in seeing personalized ads but there is no such thing. I recently had a look at what ad categories Google applies to me and honestly.. it is so wide that it is does not feel personal in the slightest, and indeed it's wide & vague and nonspecific enough that "employed male, about 30, western" would be a sufficient description. Indeed, I feel like that just filters for the ads they'd blast on broadcast media all day long anyway.
Advertisers don't really understand who I am or what I want, and Youtube history isn't a good substitute. If anything it's circular, because Youtube also keeps recommending the same shit based on viewing history..
> Yeah, all this concern with scalability, portability and clean code, has created quite a dystopian software world.
I don't see it having anything to do with scalability, portability, or clean code.
It's just cheap and (for the developers) convenient. Developers think that their software is a gift to the world, and simply getting it made (not matter how cheaply and craply and user-hostilely) is a net positive. (I wonder how many people use all these bloated things only because they pretty much have to, due to peer pressure, company requirements, etc.)
It is possible to make software that scales, is clean, portable, and doesn't rely on massive bloat.
If you're going that route, I'd focus on small & cheap SBCs. A bare, credit card sized ARM computer is probably going to be more ecological (both in manufacture and operation) than an Intel PC.
Works with any encoding and arbitrary binary data. The last byte of the length field doesn't have the high bit set, and whatever follows after that is completely irrelevant.
I haven't seen a tool that can remove fluff and clean code. And I don't like formatters, because making the rules right is too complicated. I haven't seen a formatter that won't eventually mess up code that I carefully laid out.
That looks like something I could buy. I've really wanted a tiny console PC with RS232 and ethernet for a long time now. I thought about building one into a custom keyboard using something like a raspberry pi but I haven't had the time to follow through. This thing looks like it could make my diy project unnecessary.
I also haven't found phones particularly appealing.. mine gets 5-6 days on a charge because it's mostly just an alarm clock. Any time I try to do anything with it, I get frustrated by how clumsy it is compared to an actual computer. I do like being able to look at maps or make a call in an emergency, and it's handy having a camera always in the pocket, but that's pretty much where the appeal ends.