Hacker Newsnew | past | comments | ask | show | jobs | submit | milesokeefe's commentslogin

This is amazing! I’ve been wanting this to exist for years for use in unit tests. This made my day (and maybe upcoming work week)


And cheap? Because many versions of them are on their second public generation, and not too many people are excited about them.


I was including "economically viable" under "viable". I didn't even realize there were any available on the market yet, and looking right now it looks like they're still at the $2k price point and still have mechanical issues.



Without code formatting:

>sponsorship - because I'm an immigrant

>Tech stack - I spend most of my after office hours in doing new projects, effectively, I like to use the skills learned in the job. So an advanced tech and freedom to experiment with tech is always a top preference

>sustainability - a continuous revenue-generating company or dependent on new sales every time

>motivation - be it a side project or office work, I enjoy working on the problems that are pointed out - greater the impact, more the involvement

>hierarchy - from my experience, too many levels above you is a problem not just in career growth but also product implementations, which kills the pace and transparency

>compensation - a 20% hike is the least I expect


A well placed/camouflaged trail cam or two might work.


Auth0 isn't a password manager. It's an authorization platform. If they stole Auth0 API secret keys and/or saved logins to the Auth0 management portal, they'd have access to other users' accounts but not passwords.


Seems a big reason for that was the lack of maturity in the node module ecosystem 6-7 years ago.

From the interview:

"How do we gone down a PHP root? I think from a product point of view, we'd probably be a lot further along than we are now, because in the PHP ecosystem much like in the Ruby ecosystem, or even the Python ecosystem to some extent, this tooling is well understood. It has evolved over a long amount of time. You have your defaults that just work. You have your libraries, which have been time-tested, proven they're great.

Whereas in end of 2012, beginning of 2013 starting out into the node.js ecosystem, pretty Wild West. There's not a lot of stuff going on. There was barely a usable authentication library that we could start working with. Even to this day, it's not – there's a lot of things where if you were working in Ruby or PHP you’d go, “Yeah. Obviously, I'll just grab this library that everyone uses.” Whereas in node you go, “I can't believe that doesn't exist.”

I think when we wrote the first version of Ghost that wasn't a usable RSS library for parsing XML and delivering RSS feeds in node, and that was just mind boggling. Then that has repeated enough times to where it really slowed us down."


What technical issues/deficiencies have you seen with Hulu?


On Apple TV I run into constant "cannot be played" errors that go away after hitting the menu button and reslecting the same item.


Forgotten positions in videos, forgotten ad load histories, terrible app UX, app hanging, buffering delays when scrubbing.


I've found AntD's table to be able to do all these things.

There are some gotchas with column widths when using horizontal scrolling with fixed header and fixed column(s), but it works.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: