HN user

ibrault

94 karma
Posts0
Comments54
View on HN
No posts found.

Depends on what you're working on and on if you're defining "getting stuff done" on a macro or micro scale. For large flagship missions, 2 years is nothing. The scale of work and level of verification required by these projects is massive and takes time. You've only got one shot to get things right with billions of dollars on the line, don't rush it.

I have not seen any indication that private messages are included in this. As the person indicates, phone numbers are only included if they were posted on Parler by the users themselves, but yes from what I can tell the IDs are the most "private" part of the leak. Although one could argue that they are still "public" given that Parler publicly exposed the information.

It's just a simple fact of polling. Your conclusion also completely ignores the influence of money and lobbying in setting party platform and policy.

Actix Web 3.0 6 years ago

To be fair, I believe the controversy began with disagreements over the previous maintainer's use of unsafe and spiraled from there. So not entirely non-technical.

Thank you Salvatore! You have been an inspiration to me as a young programmer and have opened my eyes to the wonders of OSS. Excited to see whatever you do next!

Not a lander but NASA has 2 potential Venus missions in their proposed Discovery missions! [0]

In regards to why not a lander: I would guess it's because it's not really necessary? Orbiters (like the proposed ones above) can gather all of the science that's really necessary to study a planet like Venus. Landers are useful to study more micro-scale science to, for example, search for life (see the Mars rovers/landers and the proposed Europa lander). And orbiters are significantly cheaper and easier to make. Landing on Mars is really really really hard! I can assume it would only be harder on Venus.

[0] https://www.nasa.gov/press-release/nasa-selects-four-possibl...

I can testify first-hand that the "functions in a single page" and "avoid the pre-processor" rules are not followed very closely haha

Yes, I figured I probably wasn't clear enough. I agree with the points in the article but I'm referring to a different situation. For example, the one that kills me every morning is where the 101 S turns into the 134, there are 2 dedicated lanes for the 134 on-ramp (so no zipper merge) but people wait until the last possible minute to force their way into the dedicated lanes and clog both those and the surrounding ones. Similar situation where the 170 S hits the 134.

Another thing I'd be interested in seeing modeled are the people who squeeze into an exit lane at the very last minute. I've only ever commuted in the LA area but it's one of the biggest contributors to traffic by the freeway interchanges.

I can write code when I'm listening to music perfectly fine but as soon as I need to document anything, like a docstring, informative comment, etc. I need to pause the music, my brain just shuts down as soon as it needs to switch to writing English.

Also in SoCal and I've noticed Google Maps has really regressed, I've gotten a ton of "faster route available" prompts that lead to significantly slower routes when on the 405 and 10.

Just to tack on with some more typographic constructive criticism (although I think the font size looks fine on my laptop), you should definitely increase the line-height of the paragraphs.

I don't think they're trying to argue that Uber and Lyft created LA traffic but I would agree that their arrival put more cars on the roads. There's a huge market of people who are willing to pay a little extra to avoid the hassle of LA public transportation and considering that, in general, people Uber to busy places (LAX, downtown, etc.), it's bringing more cars onto the already clogged roads that wouldn't be there otherwise.

+1 to HillRat's answer (especially hacking around in Codepen). On top of his, I want to plug the Mozilla Web Docs [0]. They're absolutely wonderful to reference for all your CSS needs, especially if you learn well from reading the docs. On top of that, they have excellent tutorials as well. I would consider checking out their one on CSS [1], you might find it easier to get through than an O'Reilly book.

A little unrelated but as someone who also loves their C++ and low-level programming I really enjoyed Lin Clark's articles on Firefox's Stylo [2] and WebRender [3], I think they do a great job of intuitively explaining the back-end behind CSS rendering, if that's of any interest to you.

[0] https://developer.mozilla.org/en-US/

[1] https://developer.mozilla.org/en-US/docs/Learn/CSS

[2] https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en...

[3] https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-f...

CMake has fantastic support for Qt. Decided to add a Qt GUI to a personal project with an existing CMake build setup and the integration was very painless, just ~4 lines added. Finding the solution was a little tougher, however, since nearly all documentation assumes a QtCreator + qmake configuration.