fullstackchris

While I'll take a bite at this, I think it's also fair to say how poorly portable C is. Can an mobile or web engineer quickly take some C code and use it in their stack somehow? I would guess not. While it's indeed an important lesson to see the speed of some of these 'close to the metal' languages, the question of how practical they are to use is a different question.

And if you wrote your instructions in assembly, it would be even faster!

/s

Sorry for the rude sarcasm, but isn't this a post truly just about the efficiency pitfalls of Python? (or any language / framework choice for that matter)

Of course modern computers are lightning fast. The overhead of every language, framework, and tool will add significant additional compute however, reducing this lightning speed more and more with each complex abstraction level.

I don't know, I guess I'm just surprised this post is so popular, this stuff seems quite obvious.

Is this achievable by the size of the craft itself? Or the fact that these bigger planes have 1000s of engineers behind them optimizing every possible factor to squeak out the best possible lift to drag ratio?

React / Vue is also irrelevant here however. It all depends how your actual prod code is built in the end. (For example you can use React with Next.js and still do all the SSR SSG stuff) In this case you're writing React for your server side rendered pages as opposed to the 'traditional' pattern of an SPA where everything happens in the client.

I used Perl in gradschool and it still has a special place in my heart. You're right: for reading / writing files it is excellent, and I've never seen a faster tool for those tasks either (okay, unless you want to write in C )

The double challenge here is doing this all whilst essentially keeping it in the background out of any customer sight. Even if you know exactly what you need after a while from a business perspective, you still need to reimplement it in a way that doesn't cause your product / service / platform to lose customers. I find this always to be an extreme challenge. It's a bit of a treadmill too: doing it this way (without causing breaking changes) certainly takes longer too. So it all piles up into a big messy stack of work :)

Race as an entire concept to me has always been stupid at best. Sure, there are vast swaths of biological similarities (typically, though not necessarily) according to general geographic regions of the globe, but the real mistake was trying to give this vague concept a label. Can anybody give a definition of what "white" or "black" REALLY means? It's an impossible task. If we're talking just visually about skin color, congratulations, that represents citizens of some 100+ odd countries on the planet and just as many (if not many more!) cultures and languages. But leave it to humans to try and over optimize and try to denote evermore meaningless abstractions...

Let the social "culture war" rage on. The only war I see going on in the west (U.S. mostly) is a _lack_ of culture.

I don't want to be that guy... but I'm going to be that guy.

Check out nano: https://en.wikipedia.org/wiki/Nano_(cryptocurrency)

Granted it is a cryptocurrency, but it is feeless and ~1 second confirmation.

I too thought it sounded like magic when I first heard of it.

Also, the browser extension you wish for exists, it's called Coil: https://coil.com/ but it simply doesn't have enough buy-in to work. The real problem with microtransactions has nothing to do about some bigwig execs or some deep state preventing it crap, it's simply that EVERYONE has to buy into it for it to work properly.

Unless you're the owner of it. Then its okay ;)

(But even then still never trust the suits)

Why are we always "surprised" by this?

Closures, event bubbling, event loop: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Even...

Basically all the things you otherwise forget about or never need to worry about when writing production JavaScript. Yawn. I sound like a curmudgeon and I am: too many interviews I've been in that involved JavaScript felt like abstracted garbage. Nevertheless, good luck!

I'm in the camp that thinks we're headed in a perpendicular direction and won't ever get to human levels of AGI with current efforts based on the simple idea that the basic tooling is wrong from first principles. I mean, most of the "progress" in AI has been due to getting better and learning how to understand a single piece of technology: neural networks.

A lot of recent neuroscience findings have shown that human brains _aren't_ just giant neural networks; in fact, they are infinitely more complex. Until we start thinking from the ground up how to build and engineer systems that reflect the human brain, we're essentially wandering around in the dark with perhaps only a piece of what we _think_ is needed for intelligence. (I'm not saying the human brain is the best engineered thing for intelligence either, but I'm saying it's one of the best examples we have to model AI after and that notion has largely been ignored)

I generally think it's hubris to spit in the face of 4 billion years of evolution thinking that some crafty neural net with X number more parameters will emerge magically as a truly generally intelligent entity - it will be a strange abomination at best.

I always had the idea that before jumping to quantum, it would make sense to use photons for as many components as possible instead of the relatively slower, heavier, and much hotter electron.

I don't know enough about computing hardware to know how feasible each component is to be refactored this way, but it is indeed exciting. You could almost imagine such a "photon computer" as a computer which uses little to no energy (at least for the actual computing part), is extremly lightweight due to lightweight components, and never gets hot!

> This other company, however, gave me feedback that "if this was how you worked on a team, it'd be perfect, and we love it. But in an interview, that's not what we want"

The tech interview process is still so completely broken in my book. Nobody really knows what anybody wants or how to show it 1 hour blocks (for both parties - applicant and employer)

This is more or less the concept of time, correct? I think an AI can understand state in simple cases (i.e. it can likely answer correctly "I didn't water my plant in 2 months, is it dead?"), but the way the current models are designed its just request / response, they perhaps from the very root way of how they are implemented don't (or can't) have a sort of _narrative_ sense of state. This is also present when you have a conversation with them. They won't bring up topics from the start or earlier part of the conversation, because they don't really "know" they happened. They simply receive and reply, that doesn't actually change the state of the model itself. To me this is one of the main keys that still need to be unlocked in AI capabilities. You need a neural net to modify itself in real time and track those changes to be able to have this sense.

To provide an example, it's almost like you need a _time series_ of GPT-3s, not just a single GPT-3 neural network, and the model itself would need to be able to self-inspect those time series and say to itself "ah yes, this was my old foolish understanding, now I have this new, better, understanding". I have no idea how this would look in technical terms, these are just the musings of a somewhat more-than-casual AI observer.

I mean anything coming from GitHub is anyway public. (Except for private repos of course)

But HOW can this work? It MUST have config level access to each machine, that's the only way I can see this working. I guess I just have to try it to see.

OK, reading the comments it is a totally different product, but I guess I have to try it!

"Zero config VPN. Installs on any device in minutes, manages firewall rules for you, and works from anywhere."

Okay... at first I said to myself, _no way_. But then I thought, "Any sufficiently advanced technology is indistinguishable from magic."

Crap... is this literally the product I've been MVPing the past few weeks? (https://kurynt.com) - or do I still have a chance?

Full disclosure - there is little to no functionality yet, but the homepage is enough

Hi! Saw your remarks about the difficulty of maintaining mobile apps - I agree this is an extremely large overhead, Apple and Google make it an absolute pain most of the time, but if you are willing to put in initial effort to port the screens / main functionality to a mobile friendly website, you can create a hybrid app through a WebView and significantly reduce the shipping times / app store burdens (and most updates, if not all, can go through the web and thus webview, instead of having to build and ship a native app(s)!)

If it helps. I don't know the technicalities of the mobile app at all, i.e. how many native functionalities the mobile app needs, if any.

> I mean, guys seriously.

But we're serious. OP has created their own nonsensical boundaries with these constraints. Essentially the title is completely misleading apart from the 2K number. If OP is looking specifically for a linux-compatible machine they should have at least mentioned that in the title. It's no suprise at all that these types of answers are in this thread.

I saw the title, came here to offer my thoughts about mac options, when I realize that actually "not allowed" by OP's request. It's click baity and almost feels like it was designed to get a rise out of the HN crowd.

I think the true tragedy is simply trying to identify the passion and or interests of high school aged kids. It's always been true that kids of that age spend way more time trying to fit in or find their social group than anything else. And at the same time, you _can't_ know what you want to do for the rest of your life at that age. Hell, I'm one of the many who only found what they REALLY liked to do the second year of my master's program. (hint: wasn't what my degree was in)

The real joke is that college is some 4 year, very specific journey for a very specific degree, which many have said already, is often largely wasted on 'unecessary' or 'useless' knowledge. I'd love to see much more industry or real hands-on work come to universities, no matter what area of study it is. Liking to study or research in an area is almost always extremely different than actually working in that area.

The problem is instutitions (i.e. colleges and universities) are always slow to change; its the nature of institutions themselves. Not sure if any radical change is actually possible, but rather at best case a slow molding or attempting experiments over time - a similar conclusion to what McWhorter arrives at.

I love that it's considered 'adversity' - working in some of the most advanced labs in the world, on some of the most wealthy campuses in the world, all the while partying with your friends, doing the minimum work to get a B or C average.

Not saying I was exactly one of those types, but those types ALSO got jobs just fine, and I'm ready to brawl anyone that says they faced any true 'adversity'.

Definitely. Part of this priviledge should truly be sharing your knowledge and helping others in need. It's almost a given in my book.

I'm very much hoping it's a phase and not a permanant thing... I'm still very much patriotic because of stuff the U.S. has acheived in terms of science, engineering, and of course culturally, but recently I'm not so sure what the future trend of US is going to be.

The fact that most comment threads for this post exist baffels me... it's like... 'lets analyze confrontation and create weird uncanny formulas for what are complex and always spontaneous human interactions' I don't like it at all.

I hate to say it, but this post shows how absolutely smashed mentally some city-based Americans are. Full of anxiety, fear, and general angst about what should be normal operating behaviour as a common city resident. I'm finishing a week up with my buds in Barcelona, and everything in this post is the exact OPPOSITE of the mentality we've seen here. Friendly people, happy to chat, guys and girls alike, no concern or fear and no overwhelming motive of anything. Talking for talkings sake.

My buddies are still working and living in US but I've been living in europe for the past 6 years... and I gotta say, the US has become so weird to me, especially super "liberal" culture, if you can even call it that. People simply don't know how to talk to one another anymore. It's fucked.

But what about hooks? These essentially break this point completely. Functions that literally have (side) 'effect' in the name! (useEffect)

Over the past few years, at least on the frontend, I've found in every case what is a class could be expressed in a function or variety of functions. So yeah, still unsure about this point, maybe it was more for other software domains (backend, embedded, etc)

Funny too about what you say about 'grouping functions in some way'... I just made a post about how it makes a lot of sense to put a single function per file... with my organizing, a named folder is the only thing that 'groups' my functions together... so far this style of organization is working well for us.

https://chrisfrewin.medium.com/advanced-code-organization-pa...

I disagree. For a huge majority of projects and teams, it is infeasible to build everything in-house. The way I see it, you can either

1. take an extremely impractical amount of time reinventing the wheel in house, or

2. take a (IMO a relatively much smaller) hit when you fail to take the 10 minutes to read the breaking changes on the dependency. Read this, make fixes, and everything is working again. If you hit a major issue like this with your own tooling, you're at the mercy of your team's ability to quickly build a fix.

A refined version of this point may be something like "only use dependencies which are very well tested, documented, list known issues, and have an active community of development and releases" - don't just install any package or library because "it appears to solve my problem"

> Any function that’s not pure should be a class. Any code construct that has a different function, should have a different name.

I definitely haven't been following this... anybody else using nearly 99% of functions in their frontend work? (Typically I'm in the React TypeScript world)