_akhe

I used to plunge down hard and fast because I liked to see the bubbles.

But I realized less disturbing is better, and I started barely using the plunge - just to catch grounds when pouring.

After a while I went back to pour-over. The flavor is so much better - French press is now used for loose leaf tea and I have a lot more fun plunging.

Discord is so ban-happy they have to invent apps to keep you safe from their awful moderation. This one is particularly funny - who knew you can get banned for offending AI... only on Discord

I disagree, I think it's a failure of recruiting if you got someone into an interview who can't code "at all". That must mean nobody at the company is technical "at all" either then, if you are getting people that far along without having any clue if they even write code at all.

I don't have this problem - I can easily tell who is good and who is not good by looking at their stuff online, which repos they are contributing to and what their contribution is. I look at personal projects - I can easily tell what parts they wrote vs didn't because it's usually specific to the project.

I can tell from their blog posts and comments, especially GitHub comments - I can even see if they're pushing features at 11PM on a Friday if the obsession piece is crucial to the hire.

People who say all their work is hidden under NDA or they're new grads and haven't done anything yet - sorry, if there's nothing to view online I just wouldn't qualify you to interview.

Though I have given out 50+ code tests in my career because I had to, I would never choose to do this, if given the chance when hiring someone I would never give them a code test. I think it's an amateur move and wastes everyone's time. At its best (as in the case of CTCI interviews) it's an exclusivity filter for academics who memorized the optimal data structures for algorithms as taught in school, but the candidate might not have any of the skills needed to build app features, perform DevOps, etc. or even operate a Terminal - CTCI doesn't cover anything async, nothing about UIs, APIs, databases, services, git, design, file formats, etc. it's purely academic sport. And like I said, a good developer's work should be highly visible anyway - skip the random code test.

I would spend the recruiting effort finding specific developers using specific technologies that aligns with the role and making them excited about the opportunity rather than canvasing 1000 code tests out to anyone who applies.

Anyone know more about the "NPU" (neural processing unit)? Basically a GPU specialized for AI?

It's a 10-core CPU + 10-core GPU + 16-core "NPU" (neural processing unit) for AI all on a consumer handheld. It's like a Ferrari engine in a Honda Civic - all we know is it's going to be fast and hopefully it doesn't catch on fire.

You'll want to upgrade to produce generative content - you just don't know it yet.

Those keyboards are absolutely ridiculous, sorry.

Hahah yes

Think the play is "consumer AI". Would you really write code on an iPad? And if you do, do you use an external keyboard?

I imagine running LLMs and other AI models to produce a variety of art, music, video, etc.

Bring on the AI:

- Procedural worlds

- Realistic NPC conversations

- Dynamic and unpredictable encounters

> I always say I want AI to work offline

I'm with you, I'm most excited about this too.

Currently building an AI creative studio (make stories, art, music, videos, etc.) that runs locally/offline (https://github.com/bennyschmidt/ragdoll-studio). There is a lot of focus on cloud with LLMs but I can't see how the cost will make much sense for involved creative apps like video creation, etc. Present day users might not have high-end machines, but I think they all will pretty soon - this will make them buy them the way MMORPGs made everyone buy more RAM. Especially the artists and creators. Remember, Photoshop was once pretty difficult to run, you needed a great machine.

I can imagine offline music/movies apps, offline search engines, back office software, etc.

If you lived in San Francisco in ~2014 there was a definite startup/social media bubble. So many calendar apps. So many email apps. So many ways to "share with friends" that made no money. Millions and millions invested (wasted) lol A lot of us laughed back then and we were ultimately right about it being a funding bubble. But this is just how it works. Something is successful, everyone copies it but is usually not successful - but sometimes there is some success. So they cast a wide net, scoop up what works, leave everything else behind. It's bubbly behavior but that's how the economy "breathes" by expanding and contracting. It ultimately adds growth.

There was also a real estate bubble in the early 00s with their 0-money-down loans, infinite refis, the "good faith estimate" - they were throwing money (houses) at people because middlemen could make a lot of money off selling loans. We all know about the burst, but few talk about the fact that the big banks took over those businesses, forcing them to shut down and acquired all their assets - they scooped up what worked and left everything else behind.

It seems like every presidential cycle there's some industry or space getting all the focus and funding. This current one - Trump/Biden - was the weirdest one, we had a brief crypto bubble, but it's been mostly Old Money paying themselves through government and politics (covid, wars, "keep the government running by printing $1T" type bills). I imagine the next president will "save us" from the political bubble and embrace technology, in particular AI/LLMs. The major corporations have to get a handle on AI, so I predict a lot of money will be thrown at AI/LLMs - we're just getting started. I think we have 8 years of AI bubble ahead of us.

I'm convinced those who think LLMs are just hype haven't used them, or don't know how outdated most back office processes are, and don't realize how limited we are in terms of content. I would say the bubble is just barely forming, not about to burst for several more years.

Reasons:

- OpenAI lobbying trying to get open source competition banned

- Apple releasing the M4 with those hardware specs

- Big brands like Adobe finding early success

- Industries are ripe for disruption: Medical, legal, procurement, communications of various kinds especially around documentation, support, summarizing, education, media, art, music, film and other entertainment, I can imagine a lot of disruption.

What would this do to Netflix:

  render a 100-hour Harry Potter film that follows every detail of the books exactly 

Or:

  render a Tom Cruise sci-fi movie starring Sigourney Weaver in her prime and Bruce Willis as the villain 

How could Netflix or even YouTube keep up with scripts that render any video you can imagine? They'll have to offer it too, or go the way of Blockbuster. I imagine record labels and film studios will sue and try to get certain models banned that imitate celebrities or film styles, but people will just illicitly share models with torrents. There's going to be a whole era, I think, because the tech will need to be captured by the big boys but it's not there yet - so part of that is letting the market come up with ideas before they absorb it all then burst the economy.

Our search engines and websites will have LLMs imbued into their functionality, smartphones will have them, kiosks IRL will have them, SaaS will use them to replace representatives and online order forms.

IMO AI models are potentially more disruptive than social media and crypto because it's not just the sharing of content unrestricted, it's the unrestricted creation of content and information itself - giving basically anyone the ability to do it.

Bring on AI art, music, & games!

It's an awesome way to learn :) Well either way, cool project

They're also backed by the CIA lol. To your point, I should have said "NoSQL" not "MongoDB" per se. I took the question to mean "Why not SQL" but they could very well be asking "Why not another NoSQL"

To me the syntax is the least problematic - Ruby, Python, Node, PHP... they're not that different looking syntax-wise.

For me it's definitely the CLI, package manager, and other devops around using the language that makes the context-switching tougher. npm vs gem vs pip and the fact that they all kinda work differently: npm will install libs into a "node_modules" folder in every project (so you could have 45 copies of React) where other package managers might install 1 copy system wide and your project just references it, so it affects how you deal with version mismatches. nvm vs rbenv vs venv/pyenv - slight nuances there too.

Case in point try using Angular as a React dev. You're still in JavaScript, but the CLI part is different and more involved, the @ decorator syntax and other paradigms look/feel nothing like the React ecosystem.

Getting into compiled languages there's usually a heavy IDE component you need to use and be good at (thinking of iOS/Xcode, or whatever C/C++ devs are using).

But once I'm to the point of writing in a code file and I can easily run it and see my changes, I'm good at that point.

Tips: LLMs are great translators. An LLM sidekick to accompany work outside your normal language or framework is extremely useful - can't recommend it enough. Not only will you get bespoke code examples but it will explain the "why" behind certain things that are foreign to you.

And of course, just spend a lot of time coding in the language you want to make less mistakes in.

Why MongoDB?

1. Speed: NoSQL is way faster than SQL for most access

2. Ease: Dev time is lower as the data is kept in the way you'll use it, not in relational tables - skip the ORM, skip the db migrations, etc.

3. You need NoSQL at scale anyway: As the sole db of an app, NoSQL isn't ideal at scale because of data duplication and storage size. But when/if you need to add SQL you probably still keep the NoSQL too for the faster access, storing temp data, etc. Most companies use both SQL and NoSQL.

Scenario:

Imagine an API for a video game that fetches data for an Auction House type feature. If every single time your millions of players were running SQL queries, it would be an incredibly slow and expensive feature. Much better to have that data cached in a NoSQL layer so people can access it quickly/concurrently, and only periodically hit SQL to populate out NoSQL caches. Could also use an ORM with SQL, or another in-memory solution, but NoSQL is nice if there are many nodes or maybe due to your cloud setup you can't run it in memory.

Really is not a "SQL vs NoSQL" you use both for different things. To me at this point it doesn't matter if someone "starts with" SQL or NoSQL, in almost all cases I would use both eventually. For hobby projects, even a slight preference toward NoSQL for ease of use and data flexibility, but getting into subjective territory. Sequelize is just as cool/easy

Haha so true. I noticed there's a part of HN that hates JavaScript and NoSQL.

Usually for bad reasons like a false dichotomy between SQL & NoSQL (you usually want both) or some performance comment about JS when they're using like a Rails, Django, or Laravel (some old/slow cult framework that doesn't hold a candle to Node).

Feels like Rust found its place with Next.js' Turbopack (basically Webpack but in Rust), and is good for use cases like that. I think reinventing wheels in other languages makes sense when they bring obvious value like performance or some convenience - and this Show HN fits that description.

Like someone else said - it might've been even cooler as not a re-write but a new approach in Node.

I would love to see Node eat more of Linux personally. To me JavaScript is like the "English" of programming (C is "Latin"?), with JSON being the standard transfer format and the browser being a major (if not the major) platform. Not to mention it's by far the most performant of the dynamic web languages (compared with PHP, Ruby, Python).

I run a server on a Raspberry Pi at home, but since I have an iPhone 12 with a lot better specs than the Pi I wondered why not just run it on that (with Ubuntu ofc not iOS).

Yeah I generally agree - kinda like the Hackintosh days. Aside from novelty, it ended up being better to just build what you need from scratch for a lot cheaper, and with better support.

Thanks!

This is awesome, thanks!

Yeah, I love the Pi for this reason, most upgrades are a matter of ordering the parts, like building a PC back in the day. Sometimes I look at my web server though (rpi 4), with its small size and touch screen already looking like a smartphone, and wondering if I could have just used an iPhone to host these sites & APIs on.

  iPhone 12
  Apple A14 Bionic @ 2.99 GHz
  1 Processor, 6 Cores
  5.60 GB

  Raspberry Pi 4
  ARM BCM2711 @ 1.50 GHz
  1 Processor, 4 Cores
  1.77 GB

I think iPhone always outperforms Raspberry Pi: https://browser.geekbench.com/v5/cpu/compare/4581331?baselin...

Which makes sense since it was $1000 and the Pi was $35.

I figured it might not make the most sense, but I can't help but wonder if the hardware is good enough for static sites & APIs.

Can you elaborate on why? If both devices run the same OS wouldn't it just come down to hardware needs?

I ask because I'm seriously considering trying with an iPhone 12 but wonder if something glaring will get in the way or make it not ideal.

The way you're talking (Linux is a "slow complicated OS") means you're likely some dark wizard in a tower somewhere inventing either the apocalypse or the next great consumer experience.

For that reason I thank you for your likely many contributions to obscure open source projects and gosh speed on your endeavors.

And one day you realize wrappers are what it was all about

You betta lose yaself in the music tha moment you own it you betta neva let it go (go (go (go))) you only get 1 shot do NAHT miss ya chance to blow cuz oppatunity comes once inna lifetime (you betta) /gunshot noise

On lice/louse:

When it's plural as in "lice" it's an obvious problem to be eradicated.

But why in the singular form of "louse" do I suddenly imagine a Fantastic Mr. Fox character? A little guy holding a tiny briefcase waiting for the bus in Louse Land.

It should be the opposite, because looking at lots of them is like "Ahh rolly pollies! Cool!"

But if you zoom in on one's face... you notice some ancient trilobyte Alien 3 finger fangs rapidly shoving microbes into its pie hole, who knows what kind of monster this thing is to all the hapless beings down on its level.

The spider doesn't care about any of this shit, he's just like: "Not in my house, louse." before spinning him up in his butt threads and draining his blood like a literal vampire.

Nature is awesome.

> not what I meant

> the libs are all in C

Yeah node uses bindings too, examples:

node-llama-cpp (C++)... node-SDL (C)...

Why wouldn't it also be true for mechatronics? Have some native bindings for C libraries then you can write Node or Python and still use the machine code where needed. Speaking of which:

> The speed of the underlying execution is not meaningfully affected by the speed of the Python interpreter

Wouldn't both JIT vs not JIT have an impact on speed, and also some of the "heuristical" stuff V8 does?

I wouldn't rule out JavaScript for mechatronics, everything ends up in JavaScript.