tobz

Hadn't heard of Fabworks until today. Testing out a quote on some parts I was looking at getting from OSH Cut, they're actually much better on pricing _and_ have more capabilities. (!)

Have you used them a lot? Curious what your experience with them is if you're willing to share.

If it's all sheet metal-esque pieces, where you could suffice with just laser cut features and/or simple bends.. then you should take a look at OSH Cut.

They have a fairly powerful platform -- instant quoting from uploaded design files, 2D/3D views, DFM feedback, good turnaround times, etc -- and the pricing isn't half bad for prototyping... but might not be as good for large-scale runs compared to bigger shops where you can nail down volume pricing discounts.

Regarding safety, do you have any links around the test results for the Kioma, or other car seats? You've mentioned a lot about the safety scores/test results in comparison to other car seats, but I couldn't seem to find a single mention of that stuff on the website? I also tried to see if something like Consumer Reports had a review of a Kioma car seat (either the current one or the carbon fiber one) but they had nothing.

It feels more than a little bit coincidental to call it Noria when https://github.com/mit-pdos/noria exists (and has been posted about here on HN)... especially with the whole bit about incrementally computing changes.

One crucial difference I was able to spot is that Demikernel seems to have an approach that can work for OSes other than Linux. To wit, examples of the performance of the Demikernel approach are shown on a Windows system running in Azure.

Of the three examples you listed, none of them seem to support their kernel bypass capabilities in anything other than Linux.

Doesn't seem very productive to speak on behalf of two folks who you clearly don't have the authority to speak on behalf of. ¯\_(ツ)_/¯

Agreed.

Others have mentioned that the article calls out ignoring traditional in-memory cache daemons because of the additional network time, but with a targeted p50 response time (of their HTTP service fronting all of this), and caches like Redis and memcached being able to respond in hundreds of microseconds... it does feel like they didn't actually run the numbers.

The other natural alternative would simply be to run Redis/memcached and colocate this HTTP service on the same box. Now your "network latency" component is almost entirely negligible, and you've deferred the work of managing memory to applications _designed_ around doing so.

This.

We need more community/company interaction in Rust, especially in the networking space, instead of parallel implementations.

Heh, this is funny... I worked on an emulator for Dark Age of Camelot _and_ an emulator for World of Warcraft (WCell) and attribute experience from both projects to getting my first software gig.

I also remember (fondly) going through RunUO with .NET Reflector to pick up tips and tricks. :)

You beat me to it! :)

https://cabforum.org/baseline-requirements-documents/

Sidenote: not that I think you are personally attacking them, but BuzzFeed does have some quality investigative journalism.

Listicles and clickbait help pay the bills, and I didn't believe it when I was informed the first time, but... it exists. Probably wouldn't be able to continue without the clickbait ad revenue, though, heh. :P

Just had to say that this is probably the best explanation of Reed-Solomon I've seen: practical explanations, useful visuals, good pacing, just enough humor. :)

Nice username... :)

It's totally logical, but wildly scary sounding. Is there any sort of anesthesia that is delivered which... I don't know... changes your perception as the patient to not think about the fact someone is poking your brain?

Clearly they can eliminate the local feeling of the surgery, but how do you stop people from freakinggggggg out that it's happening? :P

Since we're playing the "here's an issue I have with what you just said" game...

You "laid your cards out on the table" -- which, as you note, is likely grounds for some sort of legal proceedings -- and it turned out.. I don't know even know. You got lucky that you weren't sued, as you willfully trampled through anti-discrimination laws. Why did it take some sort of put-it-on-the-line moment for you to consider the candidate beyond their physical disability?

You even go on to say that if the candidate was "ethically challenged", your company might suffer. You admit here that you were considering not hiring them because of a disability. How is it ethically challenged to possibly fight back over a dismissal based on being in a protected class? Do you view people with disabilities as simply a liability to companies?

Your closing sentences really smack of backdoor bragging. Good thing he found you, how lucky of him, someone that would tell him flat out to his face that they were worried he couldn't perform his job... and then decided to grace him with employment.

As the OP said, really mature. :/

I'd say that this is roughly the case with .NET, in terms of async/await.

IIRC, you're using a thread pool under the hood, and you sort of have to opt-in: if you're trying to write your own async code, for example, you need to schedule it in a way that's slightly more complicated than just saying `go myFunc()`, but it's possible.

As for the JVM, libraries like Akka and Quasar already provide this, although possibly not as performantly as if the runtime itself provided it?

Very delayed follow-up, but I wanted to respond: you're 100% right.

Any progress at all is better than no progress. If being able to deal with social interactions by utilizing a cheat day helps stick to the diet -- helping to shutdown excuses, helping to be the "weekend" at the end of a long work week, etc -- then that's a useful model to adopt.

Keto relies on being in ketogenesis, which is affected by intake.

You can certainly have a "cheat" meal of higher-than-normal carb intake, but you might get knocked out of keto for a few days. If you cheat every week, you could be screwing yourself out of progress.

Can confirm: this is an incredibly low-barrier-to-entry thing.

I'm a U.S. citizen, so I signed up with Be The Match. Four cheek swabs that they send you in the mail. Swab your cheeks, package them up, send them back.

I got notified that I was a preliminary match just five months after signing up. Sadly, I wasn't a full match (hopefully someone else was!) after going through the blood draw.

All in all, it cost me nothing monetarily and maybe 3 hours total between questionnaires and the blood draw when I got matched.

By the same token, moving to an area with a high CoL could be restricting if you lost your employment and had to scramble to find a new job.

It cuts both ways.

If "this approach" is using Java/Spark, instead of something that is a smaller binary, then there are some easy answers to your questions:

- people don't want to write C (or K, or whatever yields a small binary)

- the cost of switching languages is not worth the speed-up

- it's already fast enough

I don't think you're wrong, overall, that, specifically, kdb can be much faster than an equivalently sized Spark cluster, but simply being faster does not invalidate other approaches, which is what you seem to be arguing for.

I think you're trivializing even the required effort to coordinate two cars, let alone multiple cars.

How do you direct the signal to only cars in your lane? In your direction of travel? How much efficiency is lost if all of the drivers don't give themselves enough space between the car in front of them and their own vehicle? Now they have to wait to move forward. How do you get all drivers to roll forward together at the same rate of acceleration?

You could have the last few questions handled by a computer, but you'd still have to overcome a lot of other hurdles (namely location awareness, peer-to-peer communication, infrastructure changes to road signals if you don't have self-driving cars which can detect light states, etc) before you could even accomplish something this simple at scale.

It warned about a forward collision with a car that the driver couldn't even see.

Watching closely, the red car directly in front does not appear to slow down measurably, and certainly, their brake lights do not light up. You do, however, see the black SUV's brake lights light up.

Prediction is a strong word, to be sure. It's great when it's right, and annoying when it's wrong -- like car alarms -- but if it it fires some portion of the time when there is an actual accident imminent -- like a smoke alarm -- then it's clearly useful.

(disclaimed: not tied to Launchaco but I felt compelled to address your points)

#1 - can you provide an example of where buying/setting up a domain takes you to somewhere called "shareasale.com"? At worst, it seems like the links to the registrars (which are all legit, as far as I can tell) go through some sort of analytics/tracking service.

#2 - have you considered rephrasing your download issue as "Hey, this seems broken, and here's why: ..."?

#3 - what customizations did you expect there to be in the downloaded archive? are you not seeing the selected hero/feature/social/footer templates you selected?

#4 - while others have brought up the idea of using Bootstrap/Foundation/etc as a more familiar and tweakable base, the point is around easily making a website WITHOUT having to know or understand the underlying technologies. if you're already deadset of needing/wanting to do things yourself, the tool clearly isn't for you.

you may be unimpressed, but you could be a little more positive/helpful with explaining issues rather than writing about them in such a dismissive tone that sreams "i don't care about your thing, but let me tell you everything i think is wrong with it"

Yeah, right now, I have some dinky 2.1 speaker setup, and there's a remote control box that feeds back to the subwoofer to control the volume and expose a headphone port. I have to plug/unplug when I want to switch, and the volume control button/wheel has low resolution because it's so small.

The Reddit link uses a Windows program to do it, but I wanted it to be universal because I dual-boot, so doing it in the DAC/amplifier seemed like a better approach. :)

I'm working on a headphone stand that has a USB DAC/headphone amplifier built in, along with circuitry to detect when the headphones have been hung up, thereby switching the DAC output to a line out (to drive speakers, or whatever).

It's a shameless amalgamation of a DIY post on Reddit[1] and some design aesthetics from an existing DAC/headphone amp[2] that I really like. I'm currently at the point where the internals are close to finalized enough to order boards and do integration testing, and starting work on modeling the enclosure, which will involve some mix of CNC milling, mandrel bending and welding.

I really like throwing away money, apparently.

Blog here: https://nuclearfurnace.wordpress.com/

[1] https://www.reddit.com/r/3Dprinting/comments/529qyp/smart_he...

[2] https://www.jdslabs.com/products/151/the-element/

Yeah, putting the keys on Github seems pointless and contrived: there's no remediation to putting a known-bad key out in the open. What are you going to do: block their IP? Oh boy.

I see value in the other examples, though, because they are dead simple tripwires, and, unless AWS is scanning your instances, they should never see this and it shouldn't be a problem.

I've thought about going back to school to get a Mechanical Engineering degree, or Chemical Engineering degree.

I grew up with my father being a machinist, and eventually going on to being a QA specialist for a large defense contractor, so I've be lucky enough to be able to learn a lot when it comes to machining and designing. Spitting out a 3D design from a printer is really cool, but nothing beats slapping a chunk of steel into a Bridgeport and ending up with a precisely-milled widget.

My wife is also an engineer at one of the largest (probably largest) physical testing companies in the world, and got her Chemical Engineering degree as well. There's constantly stuff she's telling me about, problems at work, custom things she's doing, and we get pretty deep into conversation sometimes about how to best solve the problems.

The money just isn't there compared to being a software engineer, but like a lot of people have said in this thread, maybe this is just a "grass is greener" thing: these problems that I can't work on just seem that more tantalizing than being the person who is actually dealing with a backlog of them. Vacationing in other people's jobs is fun and easy, and ignores actually being that employee.

Per their post about their MySQL backup solution[1], it sounds like they sort of do this? Although it's not a slave that's ready to be promoted to master, but somehow a cold standby that is not far off from being a hot standby based on how recent the binlogs are?

The wording is a bit cryptic, but it does seem that they definitely have hot standby-esque capabilities in place, in addition to long-term storage of their incremental/full backups.

[1] https://www.facebook.com/notes/facebook-engineering/under-th...

This is a DNS outage.

If self-hosted, somewhere, you could still be screwed by having Dyn as your DNS provider.

If dev-machine-hosted, then uh, your issue tracker is no longer an issue tracker. Your build server is not a build server. All the services besides Git are not meant to operate offline in a decentralized/distributed fashion.

Library documentation, sure, that could be local. Otherwise, your assertion that all of this tools infrastructure can somehow be replicated, easily, in a way that makes the difference between working online or offline effectively zero, is nonsense.

Sure, for .NET Core, that sounds accurate. If you take the .NET ecosystem as a whole: the CLR, the tooling, the libraries, etc.. Windows is the happiest case. That's at least how I take his specific point.