This sounds like a very weird edge case and it's very easy to say this sort of statement in retrospect, but I wonder what percentage of engineers would think of testing this specific combo beforehand.
1,924 karma · joined April 27, 2015
- moon-dev-tools https://antoinemopa.github.io/moon-dev-tools/
- claydash https://claydash.com/
Github: @antoineMoPa
This sounds like a very weird edge case and it's very easy to say this sort of statement in retrospect, but I wonder what percentage of engineers would think of testing this specific combo beforehand.
Reminds me slightly of this xkcd https://xkcd.com/2128/
Just tell us you just wanted to build a big airship.
That's a good thing to keep in mind!
Maybe also: understand that colleagues are not always at the peak of this cycle.
- I have a visibility in to code, issues, features, development.
- I can eventually fork the project or use someone's fork if the main project becomes obsolete. I can also keep using the obsolete version forever. For SASS software, I can't rely on it forever.
- There is an option I eventually contribute.
- There is a greater chance of having a community with lots of blog posts, docs & Questions & answers online.
- No mandatory recurring payments.
LLMs are really good at fooling us into thinking that code comments make sense.
That's why I prefer if devs don't use copilot, but instead cherry pick good output from ChatGPT.
You also benefit from all the available js tooling (editor support for refactoring, linting, syntax highlighting, type checking, etc.).
Lastly JSX eliminates the burden of switching between the framework's template syntax and regular JS/TS when refactoring code and moving logic around.
If it works, then I wonder why these adjustments are not in default emacs.
Also I feel like performance could be improved a lot, but that's probably an issue in my particular setup.
If someone has an efficient lsp-mode + typescript-mode + eslint checks, I'd be happy to see how you achieved that.
I love the language overall. Seems like standard & easier management of dependencies and compiler flags would help it thrive again.
I'm mostly playing devil's advocate here, what I truly think is that all monitoring and analytics should require user approval a bit like cookies. E.g.: you visit a website and it would ask for permission to send monitoring data to listed sites.
Maybe next time, don't be shy about who you are in the title? Who you are is probably your greatest asset.
Show HN: Pierre.co, by Bootstrap authors @mdo and @fat
You don't really have to explain the product in the HN title, as people will want to click just to keep up with you.
Apart from this, I think the main issue with the product is that we (developers) already have & love github and/or gitlab and spent time learning it and building workflows with it, so I don't think anyone is excited currently about a new git hosting platform, unless it's 10x better - which is not clearly stated in the landing page. Pierre.co uses different paradigms, but it's not clear if they're any better. The promises are pretty vague.
Haha! Happy to see impostor syndrome goes all the way to the top of the hierarchy.
Is this an original used blackberry keyboard or a new one build specifically for this?
Who owns the trademark for this blackberry icon nowadays? Is there risk that a random company owning the trademark will sue you?
Having other people help your project might be bad for your ego, but it's also a great way to grow as a developer.