Search Hacker News by keywords, user, score, etc.
Subscribe to new search results by RSS or JSON

It goes very slow and it doesn't need to work with high resolution or long distances. It has plenty of time to average out noise.

Solid-state LIDAR is still a fairly new thing. LIDAR sensors were big, clunky, and expensive back when Tesla started their Autopilot/FSD program.

I googled a bit and found a DFR1030 solid-state LIDAR unit for 267 DKK (for one). It has a field of view of 108 degrees and an angular resolution of 0.6 degrees. It has an angle error of 3 degrees and a max distance of 300mm. It can run at 7.5-28 Hz.

Clearly fine for a floor-cleaning robot or a toy. Clearly not good enough for a car (which would need several of them).

My experience working in an automotive supplier suggest that Tesla engineers must have always knowns this and the real strategy was to provide the best ADAS experience with the cheapest sensor architecture. They certainly did achieved that goal.

There were aspirations that the bottom up approach would work with enough data, but as I learned about the kind of long tail cases that camera fused with radar data, camera only seemed categorically unsafe.

easy edge case: A self driving system cannot be inoperable due to sunlight or fog.

a more hackernew worthy consideration: calculate the angular pixel resolution required to accurately range and classify an object 100 meters away. (roughly the distance needed to safely stop if you're traveling 80mph) Now add a second camera for stereo and calculate the camera-to-camera extrinsic sensitivity you'd need to stay within to keep error sufficiently low in all temperature/road condition scenarios.

The answer is: screw that, I should just add a long range radar.

there are just so many considerations that show you need a multi-modality solution, and using human biology as a what-about-ism, doesn't translate to currently available technology.

Very distant systems, i.e. extra-gallactic, like quasars, are used for the most accurate coordinate systems (i.e. the International Celestial Reference System/Frame, ICRS/ICRF), because their angular velocities are negligible due to the huge distances where they are located.

Basing an inertial coordinate system on the observed positions of the bodies belonging to the Solar System is affected by much greater errors caused by the imperfect modeling of their movements.

Using stars that are outside the Solar System is much better, but using distant extra-gallactic objects is even better.

If we did not have the "fixed" stars as a background on which to view the movements of the Sun, Moon and planets, who knows how many centuries later physics and technology would have reached the current level, because when seeing only the relative motions of the planets, without a fixed reference system, those are much harder to understand.

I trust your and parent’s comment 1000x more than rauch and leerob and will give angular a go next time I can

yeah, try matching a human eye on dynamic range and then on angular speed and then on refocus. okay forget that.

try matching a cat's eye on those metrics. and it is much simpler that human one.

Location: Washington, DC Area. East Coast, United States Remote: I'm open to remote and on-site with no preference

Willing to relocate: Yes

Technologies: Java, Python, JavaScript, Ruby, Ruby on Rails, C++, C, a little bit of React and Angular 2

Résumé/CV: https://1drv.ms/b/c/46d1fdb68a721574/ERkpEotrOltLly0j74zyXdI...

Email: bepotts47@gmail.com

Hello! I'm a software developer with lots of experience in full stack and backend development. I was most recently a developer at SirusXM Radio until I was laid off recently. The languages I've used the most are Java, C++, Ruby ( Ruby on Rails ), Python, and JavaScript. I've also worked over a year in a classified setting and I still hold a security clearance. I'm looking for a junior/entry level software engineer position.

I attended Virginia Tech for three years and studied Computer Science and Math. I got the core CS curriculum completed; the part I didn't complete were the electives. I had to stop attending because I ran out of money.

Due to my current financial situation, unfortunately I'll require a salary position - no equity only.

With all that said, I'm open to having a conversation with anyone. Thanks! :)

Location: Greater New York Area Remote: Yes (US-based) Willing to relocate: No Services - Web development, Data engineering, Cloud sysadmin + DevOps, Software consulting, Tech leadership About Me: I’m Karan Krishnani, an independent software consultant with over 15 years of experience in full-stack development, cloud architectures, and AI integrations. I’m currently looking for projects as a fractional embedded team member (10–20 hours/week). My background includes building scalable solutions for industries like healthcare, government, and financial services.

What my last client had to say about my work: Karan is a reliable and results-oriented individual who consistently delivered high-quality work.

Technologies:

Languages: JavaScript/TypeScript, Java, Python, Swift, PHP | Frontend: React/Redux, Next.js, Vue, Angular, TailwindCSS | Backend: Node.js/Express, Apollo GraphQL, Sequelize | Cloud: AWS, Azure, GCP, Heroku, Netlify | AI/ML: Hugging Face, Jupyter, DataBricks, Transformers.js | Observability: AppDynamics, Sentry, DataDog, Grafana | Other Tools: Docker, Terraform, Figma, Git, SST

Résumé/CV: https://karankrishnani.com/resume

LinkedIn: https://linkedin.com/in/karan-krishnani

Email: karan.krishnani at gmail dot com

SEEKING WORK Location: Greater New York Area Remote: Yes (US-based) Willing to relocate: No Services - Web development, Data engineering, Cloud sysadmin + DevOps, Software consulting, Tech leadership

About Me: I’m Karan Krishnani, an independent software consultant with over 15 years of experience in full-stack development, cloud architectures, and AI integrations. I’m currently looking for projects as a fractional embedded team member (10–20 hours/week). My background includes building scalable solutions for industries like healthcare, government, and financial services.

What my last client had to say about my work: Karan is a reliable and results-oriented individual who consistently delivered high-quality work.

Technologies:

Languages: JavaScript/TypeScript, Java, Python, Swift, PHP | Frontend: React/Redux, Next.js, Vue, Angular, TailwindCSS | Backend: Node.js/Express, Apollo GraphQL, Sequelize | Cloud: AWS, Azure, GCP, Heroku, Netlify | AI/ML: Hugging Face, Jupyter, DataBricks, Transformers.js | Observability: AppDynamics, Sentry, DataDog, Grafana | Other Tools: Docker, Terraform, Figma, Git, SST

Résumé/CV: https://karankrishnani.com/resume

LinkedIn: https://linkedin.com/in/karan-krishnani

Email: karan.krishnani at gmail dot com

> As soon as they try to build any kind of container element they hit big problems.

That's not true. Web components that returns nothing will contain only their children as nodes, that's good enough for a good amount of container use cases.

It could be better, but this little annoyance is still better than React, Angular, and the other options.

I don't think that makes it as special as you think it does.

> There are huge issues in the Apple ecosystem with documentation and so much tribal knowledge.

I struggle to come up with an ecosystem where that doesn't apply. React, Angular, .NET, .... Though some of them probably even suffer from overdocumentation, e.g. React with the same beginner level tutorials / open source code regurgitating bad patterns, and you then have the challenge of separating the wheat from the chaff.

The question is really whether maintaining an ecosystem-specific model would be able outperform a better generalized coding model, and even further whether the marginal improvements would justify the additional maintenance process/cost.

Location: Spain

Remote: Yes, only remote

Willing to relocate: No

Technologies: Angular, Rust, PHP, TypeScript, RxJS, NgRx

Résumé/CV: https://www.linkedin.com/in/newmanoz/ , https://jamm.dev/resume.pdf

Email: normandiggs@gmail.com , oz@jamm.dev

I have over a decade of experience with Angular, and I teach other developers how to use every new feature, providing clear explanations to the Angular community through my [blog](https://medium.com/@eugeniyoz).

I could create a new Angular app using Nx, Angular 20, Tailwind 4, Playwright, and Vitest, making it 100% zoneless with outstanding performance and low memory consumption. Or, I could assist you in fixing bugs in an existing app, improving performance, and implementing features of any complexity.

Picnic | Multiple roles | Amsterdam, The Netherlands | Full-time | ONSITE | Visa Sponsorship & Relocation Support

Take the lead on projects that power Europe's most advanced grocery delivery tech. And without the grind of Big Tech or the chaos of early-stage startups.

Picnic now delivers groceries to millions of people across three countries and is growing quickly. This includes the tech team, which is at the core of everything from product development (mobile app, store backend, internal dev platforms, etc.) to last-mile delivery optimization using machine learning.

Everything is built in-house, and many of their solutions are open-sourced.

You’ll solve real engineering problems at scale - while shaping the systems millions rely on every week.

Here are the job openings:

- Java developer - https://jobs.picnic.app/en/vacancies/JJBXTUB0/engineering/ja...

- Senior Java developer - https://jobs.picnic.app/en/vacancies/JYMPNN6M/engineering/se...

- Machine Learning Engineer - https://jobs.picnic.app/en/vacancies/JUU31JEG/engineering/ma...

- Python Developer - https://jobs.picnic.app/en/vacancies/J3BZMZ2F/engineering/py...

- Angular Developer - https://jobs.picnic.app/en/vacancies/J5CTQURJ/engineering/an...

Love Lit. I've pushed hard for Web Components at work for a while now with some success (the shine is definitely coming off of Angular for a lot of people there) and I've only used Lit to build my personal projects for a long time.

I love it when I visit one of my pages and use Lighthouse to check it out and have nearly straight across 100 scores. Also, I usually have really great performance on phones as well because the pages are so light and quick to render.

Inner ear is a great example! I mentioned in another comment that if you want to be reductive the sensors in the inner ear - the hairs themselves - are one dimensional, but the overall sense is directly three dimensional. (In a way it's six dimensional since it includes direct information about angular momentum, but I don't think it actually has six independent degrees of freedom. E.g. it might be hard to tell the difference between spinning right-side-up and upside-down with only the inner ear, you'll need additional sense information.)

> Lit has always been designed partially as a prototype for where web component standards could go in the future.

> There is a proposal in TC39 for native signals,

Which originated (or the modern versions of signals originated) in Solid, not in Lit.

Let me quote the readme: https://github.com/tc39/proposal-signals

--- start quote ---

The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

-- end quote ---

That’s also why I really like Aurelia framework. Its component model feels very intuitive, and it embraces standards like custom elements and decorators instead of inventing new patterns. Compared to Angular’s boilerplate or React’s hook gymnastics, Aurelia lets you write less code that looks more like plain JS/HTML. Too bad Aurelia never got the same traction as the big frontend names, because the DX is really solid.

Lit is fantastic lib as a way out from legacy web framework (since can be injected in any framework including Vue, Angular, React). I used it as a way out out of old Vue2 project

For the frontend work that I did, Lit was a godsend. It really helps you build components and apps without getting in the way.

In comparison, Angular is a monster, and React is designed for the old browser capabilities, and is now staying around by inertia, not by inherent quality.

The proposal is stuck at stage 3. AFAIK, to proceed to stage 4, it needs two independent implementations, but Firefox [0] and Chromium [1] didn't see any progress in this area for about a year. Personally, after working with Angular for many years, that's not a language feature I am looking forward to.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=1781212

[1] https://issues.chromium.org/issues/42202709

Meanwhile, I've been looking for a while and if they want a full stack or a FE developer it's always, always React. Rarely if ever Angular, occasionally Vue or Svelte, and never Phoenix.

I recall back in the day when Struts was everywhere, some of us figured out it was because Struts was a trap that took twice as many devs to get anything done, and that's why there are so many openings for it. Every time I look at React, I just wonder if it is the new Struts.

The old Angular apps I worked on (heck that was before AngularJS and Angular split) was pretty decent. Long argument lists were a big problem, sure, but the whole Service layer was one of the smartest features I've seen in a framework in a while. Second only to Routes. It saved us leaking a bunch of impedance mismatches across the entire codebase. It gave us some place to stash code while we asked the backend team to change their APIs.

I've really been loving Astro lately, it's simple enough that it stays out of your way and you can host it yourself easily. Gives you nice backend + frontend with the option to drop in React, Vue, Angular, etc if you need them.

react-router if you just want a simple React frontend, write your backend in something else.

Collaborative weekly cooking planner.

It started as a fun experiment to check how quickly I will be able to deploy something robust without any prior experience or 3-5 years senior level knowledge of a new for me tech stack but with the substantial help of AI coding tools. So as I am a solo-team developer I took for the job PaaS services and easy-to-go web development tools like Vercel+NodeJS [TypeScript], Supabase, Stripe and for AI co-piloting at first Cursor and after a month - Claude code.

The product has wide range of features: Calendar for planning and assigning meals, recipes library, AI recipes extractor from TikTok videos and from plain text instructions, recipes editing of ingredients instructions calories etc., invitation logic for adding collaborators into your calendar dashboard to share recipes and split days of cooking, automatically generated grocery list for purchasing easily required ingredients.

The tool is fun to use and we are using it with my wife as first beta testers the last couple of months.

It took me about 50 days by 1-4 hours a day of work that is around I would say 130-ish hours with 9-to-5 job and spending sometimes half, sometimes all weekends for resting.

I could deploy much earlier but I decided to make proper e2e tests, by taking user's security seriously applied RLS policies and carefully considered backend apis to avoid any potential data leaks. Also foreign tables and supabase wrappers were a completely new concept for me so it took me some time to figure out how to properly configure everything.

I used a proper dev environment and blocked tools access to production for co-pilot as it wanted to reset at any new migration my database . Also I took under control AI and most of the time planning session lasted 5-10 iterations until we understood each other clearly, so maybe 80% was planning and probably only 20% for coding if not less. My coding contributions were minimum - I wrote maybe 5% of the code. Database functions, security definers, RLSs were hard to grasp by AI in the context of my app user stories so I did it by 80-90% myself and asked Claude to finish it under my control.

P.S. Frankly speaking I of course did a lot of "toys" before with plain Javascript, Angular and HTMX. MySQL is kinda similar at some degree with PostgreSQL so its not like I had 0 experience at all. Also I don't know but I feel like the biggest asset even not a prior experience with some tools but knowledge of overall software development patterns, what each task requires and how to avoid messy situations, keep things simple but robust at the same time.

Location: Helsinki, Finland

Remote: Yes

Willing to relocate: Only to USA :)

Technologies: .NET/C# (Azure, ASP.NET, WPF), React, Angular, Typescript, mssql/postgres(really any SQL DB)

Always willing to learn new things, but my area of comfort and expertise is .NET/C# and on the frontend side React.

Résumé/CV: https://www.linkedin.com/in/shahindohan

(Can share PDF version if someone is interested!)

Email: shahin.dohan/at/gmail

Cheers!

> Next.js is easily the worst technology I've ever used.

To be fair, this is partly on the kind of people who use it. E.g. if you're trying to build something that's intended to last for 10+ years but you don't think it's worth it to spend the 20 hours watching the Udemy course on Angular, then your technology is going to be a complete dumpster fire no matter which stack you choose.

> If you compare those solutions with the old model that made NodeJS / React SPA get so popular, so fast: Buffet-style tooling/libraries. You basically build your own swiss army knife out of spare parts. Since all the spare parts are self-contained they have to target really low abstraction levels (like React as a component library, HTTP+Express as a backend router, Postgres as DB).

I have done a few Angular apps and the experience/setup quoted above is basically foreign to me. I know that it is a framework and not a library but it is a very well designed framework (atleast Angular 2 onwards; I used Angular v20 for my latest component). Basically most of the commonly needed stuff is included in the framework (I just added NGXLogger for logging) and the abstractions are pretty nice and fairly similar to a backend service (services wrap libraries and components rely on services). RxJS can be a bit of a learning curve but once you are comfortable with the basics, it can take you quite far. Atleast I rarely had to fight with the framework for typical SPAs. Also, the documentation along with tutorials is great - I learned using the tour of heroes application[0] but seems angular.dev[1] is the new home for v20 docs.

[0]: https://v17.angular.io/tutorial/tour-of-heroes

[1]: https://angular.dev/

Adding on to the other comments here about Next.js vs Remix.js.

We had to choose a framework for our new app last year and were researching the current state of things. Next.js was / is by far the most popular, but also had some of the worst feedback and caution to stay away. Remix isn't perfect, but I appreciate less abstractions and working with simple request / response structures.

Also, a warning for those hiring for frontend / fullstack roles:

Over the years when hiring for roles for X frontend framework, we would constantly find "experts" in framework X that would really impress us. Whether it was React, Angular, Vue, Remix, etc. Then after moving forward, we found they didn't know core JS fundamentals and were basically useless beyond the framework.

As an experienced dev who has explored almost all possible JS options - including but not limited to - React, Angular, etc. and settled for Phoenix/Elixir, I can tell you nothing comes close to the peace of mind you get from just opening up a text editor, naming a module whatever the fuck you like, writing functions, piping the results, validating with `with..do..else` and the best part - catching errors at compile time. Everything just works - even after 5 years. Whereas, with JS, something keeps getting burned down every 6 months or less even if you didn't touch the code at all.

Seriously, give Elixir a shot.

I've worked on many very large Angular applications I've always loved working with it. I have worked with plenty of React but I avoid Next.js like the plague after reading through documentation / examples / blog posts.

I was in the trenches pre-ES6 with JavaScript and JS/CSS since the year they came out, so of course I do love KISS-style bare-bones websites when that is the proper tool for the job. But certainly not for anything at scale. Angular, being a framework and not a library, is perfect for those purposes. I prefer that it IS opinionated (no "what router does this project use?"), and I also would not develop anything these days without TypeScript (even small sites).

I am steering clear of all of this server-client-code-same-file stuff ... seems like madness to me. To each their own.