thrwaeasddsaf
Joined 5 years ago
Joined 5 years ago
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 absolutely are cars for which it is difficult to get some aftermarket parts but this isn't a good example.
That's the great part, I get to choose instead of being forced to the same regular pollute every day.
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.
Very secure but not in my hands. No thanks.
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.
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.
https://en.wikipedia.org/wiki/Monad_(functional_programming)...
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.
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.
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.
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.