HN user

LordHeini

737 karma
Posts0
Comments229
View on HN
No posts found.

Adding a long strand of Filament in z direction is what the Author of this article tried. By injecting molten filament into a long channel in the infill.

What i meant that the z-direction does not need to be MORE stable than the other directions.

Adding a long strand of filament in the z-direction in the infill (close to the geometric center of the print) might make the print more resistant to stretching but not necessarily bending.

Carbon rods don't bend but filament does. The wing would break apart at the seams event if it had channels of filament along side its z-axis. It would still be more stable, but not as much as one might think.

Walls give a print most of its strength by a huge margin. And interlocking the walls in z-direction would have a proprietorially larger impact.

I doubt that filling a long thin channel will ever work. The heat + pressure will always collapse the thin infill walls.

In general infills does not provide much strength to a part, it is way better to have stronger walls.

And z-direction does not need to be more stable than the other directions so there is no need for long continuous strands anyway.

Maybe it would work better with smaller, less tall, slots at the inside of the walls.

Lets say 2-3 layer heights tall, continuously filled slots, which are then interleaved with each other. More like bricks less like columns. The outer wall layers would provide stability to prevent collapse. And over spill or bulging would occur towards the inside of the part.

I think, the cost of running and training models is going to fall due to Moore's law and friends.

That also meas that the worth of today's computers declines rapidly and all the money invested in compute power with it.

Compute is basically what the AI VC money is spend on. That money will be gone in a few years due to the hardware being worthless.

On the other side running a model (locally) will become cheaper and cheaper to the point that Ai stuff becomes a everyday commodity running on cheapo devices everywhere.

Then there are optimizations too. Which lowers the cost.

So it's not going away and it's not going to be expensive for the consumer in the long run.

My 5 year old rtx 2027 runs models those output would have been state of the art a couple of years ago. In a few years something running on the level of today's top models might run under your desk if that progress goes on at this pace.

I assume an adblocker can remove those.

That would be a net benefit because pages requesting location for no reason end up in the block list and don't annoy me anymore.

No the filler placement is sort of a cultural or historical thing.

Usually European cars have filler on the passenger side while American and Japanese put them on the driver side.

Afaik passenger side fillers are more safe if you run out of gas and need to fill up from a canister at the side of the road.

While driver side fillers are more comfortable because you don't have to walk as far to get there.

For your V2: a Can-Bus connector would be great. Should really be standard for toolheads nowadays. Makes cable management so much easyer. And the board does not need the driver for the extruder, the heater contoll and sensors anymore.

So maybe a version which is optimized for Can-Bus toolheads?

And more driver slots, 4 is not sufficient if you want a self leveling bed.

Vorons need 4 drivers for the gantry alone.

Or as my mom used to say: AEG auspacken, einschalten, geht nicht.

Which translates to: unpack, switch on, doesnt work.

She owned a couple of AEG devices and all broke immediately except the oven. AEG ovens and stove tops seem to be mostly OK for whatever reason.

I definitely don't want to be randomly interrupted by Ai garbage.

Those horrible automatic translations are bad enough.

And it seems the slop can't be completely disabled. I guess sooner or later it will spew out"usefull recommendations" and end up being just another vehicle for ads.

It will be shit like "did you know that the singer of band {xyz} likes this brand of {snake oil}?" or "the song you are listening to reminds me of {insert crypto scam}".

It seems soon antoher browser plug-in is required to get rid of yet antoher annoying anti-feature.

FiDA is a planned initiative that forces first party financial services like banks to provide other services like insurances or investment companies and maybe third parties with their customers data.

From what i understand it is required that this works via a unified API across all of Europe.

Data transfer explicitly requires the customers consent.

My guess is that this would be useful if you change the bank or some insurance to allow easy switchovers and of course tax avoidance and money laundering might be harder.

IMHO insurance companies should not have access to any of their customers banking data (they want to of course, to do price gauging and price discrimination).

And obviously there is no reason why any of those vile datahogs like Google, Facebook, Apple and so on, should have even the slightest access to this.

Its not too hard to detect ads in video streams, even old school analog VCR's could do that.

Watching TV shows without adds was one of the selling points of those back in the day.

Some more modern digital ones had near real time features where they would play with a delay of a lets say half an hour and used that time to remove the ads.

If you have stream from Youtube containing ads you can trivially skip ahead.

And Youtube could do nothing about it because random skipping is one of the base features of every video player ever.

Sadly noise sells.

I can totally understand that bikers like to hear the engine and exhaust of their bike but physics and the design of motorcycles is not very accommodating to that.

My bike has the manufacturers default 94db idle exhaust.

It is 94db because anything louder than that is not allowed on certain nice Austrian roads, so the manufacturer set it to 94.

While driving i hear the wind noise on the helmet, the airbox, the drive train and a bit of the engine. I usually wear ear protection.

To be clear 94db is a lot and it is way more if you pull on the gas and i don't have one of those stupid valve controlled exhausts.

I am always astonished how freaking loud that thing is, when i hear it's exhaust echoing over open fields or while going through a tunnel at full tilt.

It just comes down to physics, the exhaust points not at the biker, so the noise is directed into the environment.

There is no engine bay covering the engine and gearbox so that is comparatively loud, also chaindrives are rather noisy as well.

For the exhaust to compete it must be incredibly loud, which of course is obnoxious.

Some modern (sports) cars play engine sounds via the stereo system, maybe someone can build something similar for bikers.

In Europe new motorcycles must have ABS on both wheels since 2017.

Its a good thing.

While it is possible to stop in less distance without ABS, in real live emergency situations ABS usually is of great help due to the no skill required, additional control.

For example if you take the sudden car running in front of you from a side road. You will instinctively pull the brakes hard on a road with unknown slipperiness.

Maybe the car then stops in the last second or is really fast so there is space, then you need control to ride around the car.

You really don't want your rear wheel locking up and the bike going sideways or doing a stoppie on your front wheel which completely removes any way of obstacle avoidance.

The same is true if over breaking in a curve, if you can handle the bike standing up you can brake astonishingly hard in curves.

I would not recommend it though it feels really weird being slippery in a curve.

On rainy days i do even like traction control. It saved my ass a few times where i accelerated out of a curve a bit to enthusiastically on wet foliage.

There is another option.

- Get a (cheap) docker capable server.

- Install the OSM/Nominatim stack using docker.

Setting this up used to be a pita, but due to docker its super easy.

This has a couple of benefits.

Like fixed, predicable costs. You can whatever you want without thinking about weird API points which costs a random amount of money. You can serve whatever traffic you want and a cheap v-server gets you an astonishingly long way. There are no 3rd-party privacy issues you can just embed your maps without annoying cookie banners.

Its all about long term habits, basic knowledge about nutrition and the 80/20 rule.

Hardcore diets and then falling back to the old habits are absolutely not the way to do it. There are things like diet fatigue, the mentioned Yo-Yo effect you don't want to deal with.

Your "diet" should be generally healthy and long term sustainable. It just does not work to replace one way of malnutrition with another one.

So here are the things i (BMI 22, bodyfat < 19% for now 20+ years, at age over 40) would recommend:

One is strength based exercise. Find 1-3 days in your week where you can dependably (!) spend an hour or two to go to the gym. It is better to go once every week reliably, than to go 3 times one week and then skipping the next.

Get a full body training plan consisting of multi joint exercises. For example don't waste your time on biceps if you can do rows which trains your biceps and back at the same time.

You must do strength training order to gain muscle mass. Muscles have a large influence on your hormones, which helps to suppress hunger and keeps you fit in general. The hunger suppression is important if you lose weight. It works this way: if you lose weight, you will usually lose muscle mass alongside fat. Losing muscles creates a huge hunger signal compared to fat. Doing strength training keeps you from losing muscle (or even building it) so your hunger is lower while you lose weight.

And you don't want to end up skinny fat with issues like back pain (which i ended up with at age 20 without ever being overweight).

Don't overdo it. But be consistent, do the smallest amount necessary but every single week no exception.

Don't do cardio (at least not cardio only). Cardio is fine if you do it for sporting reasons but since you seem to be overweight, i assume this is not the case ;) So cardio would just waste your time because it burns surprisingly small amounts of calories while increasing hunger by a lot. It also does not build muscles as much so why bother?

The most important part is to get your nutrition in check.

Basically do the following:

Close to every meal should, by volume, roughly consist of 1/4 protein, like chicken or other lean meat, or plant based alternatives 1/4 carbs, like rice, potatoes whatever (pasta has tons of calories so be careful here) 2/4 vegetables like carrots, broccoli... whatever just mix it up.

It is a ton of vegetables, which is good because it keeps your stomach full and is healthy in every conceivable way.

Do not skip fats, but skip pure sugars especially in liquid form like soda.

Don't do cheat days where you mindlessly eat thousands of calories, this messes with your psyche for no reason. But eating out, or some junk food is fine from time to time you are not a robot.

Inform yourself about the calorie content of your meals and try to control the amount.

There are many ways to exert control, which are highly individual. Some have no problem skipping breakfast, some make their meals smaller, some do keto or track calories. Whatever floats your boat you have to find out. Remember it has to be sustainable. Personally i try to get a good amount of protein into my meals and i keep an eye out for calories without counting.

Every single morning: Use the toilet, step on a scale, check your weight. It varies a bit from day to day but the average helps you track. You might want to use an app but its not really necessary. This is your main way to keep track. Gain weight? Try to eat a bit less next week.

Keep in mind that you are in it for the long run. There is no need to lose tons of weight in the short term. It is fine to be slow which is way more sustainable anyway.

You want to be fit for the rest of your life so you have to keep at it for the rest of your life.

I guess the politicians don't want their Netflix to be more expensive.

Sadly its the EU and for every law there are untold numbers of lethargic and mostly incompetent beaurocrats trying to enforce it.

Those work very every slowly, but they are many and usually unstoppable when it comes to collecting money.

I am sure most people in the European parliament don't know or care what a red state is. It's one of those American things that is opaque to Europeans.

I guess they tried to find stuff to tax which does not hurt the bigger European populace.

The US biggest export is oil and they certainly want that to be cheap so no tariffs there.

And they are incapable of putting tarifst on online services and digital products.

I think that is basically the case indirectly.

Here an example with my limited understanding:

Chinese steel is super expensive in the US now, so US manufacturers buy less of it raising the cost of US products.

This makes Chinese steel more available on the world market and it becomes cheaper for everyone else.

Due to the increased cost of steel US stuff made out of said steel, is generally more expensive while everyone else's become cheaper.

So products not made in the US become cheaper in comparison and thus sell better for more profit.

Oddly enough the EU imposed counter Tariffs on some weird stuff like Alcohol and Motorcycles...

Europeans can easily replace Jim Beam in their Cola.

And Harley Davidson is insanely expensive anyway with the usual customers being by MC-Members or dentist in their midlife crisis.

That is not the case anymore.

React and many other SPA frameworks use an additional virtual DOM which gets mapped onto the real DOM. This used to be faster 10 years ago and allowed for a unified interface.

Any addon manipulating the DOM forces the virtual DOM to go out of sync thus crashing the app.

As shown be the likes of Svelte, the virtual DOM is just legacy modern browsers are fast enough to get by without.

It was absolutely worth a try.

Blender suffered the same sort of issues as FreeCAD does, but managed to get out of the slump.

It is often important to have a main player enforcing proper, unified UI/UX and fix the many small problems and bugs which drive users away. Sadly it is usually an issue with long running and highly complex open source software that it gets really fragmented. You see that in every function having its own button or workspace, inconsistent naming, functions which do the same but slightly different and things working differently depending on some context where they really should not.

Thanks to the people from Ondsel it felt like FreeCad would be on a similar route to Blender. It was way more user friendly thankfully there has been major back porting.

So there has been a lot of progress especially with the upcoming 1.0. You should give one of the Release Candidates a try. I use it for my 3D printing projects and it works pretty well.

Apart from the patent issues.

There has been some tinkering with this technique in the community.

From what I could gather this sort of bricklayer interlocking does basically nothing to help part strength.

And you can not do it on the outside walls because they would not be smooth.

Which means you would need to transition half way in the wall from stacked to interlocked which is possible but needs a very well tuned printer laying lines a fraction of the nozzle diameter.

All in all does not look like it's worth the effort.

I would agree with your sentiment.

This is basically a lib with some extra syntax to parse CSV Files.

A 'proper' DSL would require a very specific domain where it is applied to. Like document creation, or solving a certain problem and only that but not much else. Turing completeness is usually not required as well.

For example Matlab or LaTex are domain specific as well as SQL. Those are used to do math, create documents or do mangle tables.

Imho just renaming forEach to Map to parse CSV files does not fit the bill so the linked example is not that great.

This project basically a DSL builder thingy with a text processor demo.

As an aside:

I am missing the most important thing when it comes to CSV which is configuration of the input.

Might be because this is more of an example but it is usually a sign of a lets say more academic project.

Working with CSV, is usually a source of a lot of "good fun" where many hours can be spent.

Because your average CSV is often a SSV or TSV in some ISO that is everything but not UTF8. It usually contains line breaks which have been renamed to funny icons by some combo of tool and operating system. Also there are weird escape character in orders which are not consistent on every row. Also sometimes you have titles sometimes not. Dates make no sense, are language depended and in a weird format the intern made up 10 years ago. And even numbers are weird too, like 12e^-25 or '0.00' or '10.000,0'. Then you get columns which really should be 2 or more, or there are lines which span multiple rows.

Ihmo it is way better for robust CSV parsing to have a really low level approach where you rigorously check for everything (and return everything to sender that does not fit).

Apart from esthetic considerations which are more or less personal taste Comic Sans is very readable.

Things like wobly lines or non symmetric letters (p q) help readability a lot.

Many fonts for the dyslexic use similar styling techniques to avoid letters flipping for example.

Programmer fonts are usually made for readability and I would assume the same holds true there.

As someone who as written a lot of Go and trained a couple of people in it.

The "more difficult" in this quote makes me somewhat angry.

`This breaks down if JavaScript library authors are using languages that are different (and more difficult!) than JavaScript.`

JS is absolutely not easy!

It is not class oriented but uses funky prototypes, it has classes slapped on PHP-Style.

Types are bonkers, so someone bolted on TypeScript.

It has a dual wield footgun in the form of null/undefined, a repeat of the billion dollar mistake but twice!

The whole Javascript tooling and ecosystem is a giant mess with no fix in sight (hence all the rewrites).

The whole JavaScript ecosystem is ludicrously complicated with lots of opinions on everything.

Tooling is especially bad because you need a VM to run stuff (so lots of rewrites).

This is why Java never got much traction in that space too.

Go for example is way easier to learn than Javascript.

Here i mean to a level of proficiency which goes beyond making some buttons blink or load a bit of stuff from some database.

Tooling just works. There is no thought to spend on how to format stuff or which tool to use to run things.

And even somewhat difficult (and in my opinion useless) features like classes are a absent.

Want to do concurrency? Just to `go func whatever()`. Want it to communicate across threads? Use a channel it makes stuff go from A -> B.

Try this in JS you have to know concepts like Promises, WebWorkers and a VM which is not really multithreaded to begin with.

No really because the gas helium or oxygen, is super low density (in fact the lowest 2 density gasses there are). This means that you would need a compressor which can on one end suck super large volumes of gas but sill achieve high compression. Those are heavy and need lots of energy which you don't have on an airship.

I looked up some compressor manufacturers. And got roughly the following:

Large helium compressors, which compress like 2000 liters of helium per minute to 200bar, weight around 2 tons and consume power in the order of 60kw.

Not sure if 2000 liters per minute is the right amount but you get the idea.

So even if you can fit that thing on your airship, the 60kw power plant and all its accompanying fuel does not fit.

And remember you are doing this because of fuel usage the first place! So you would be using fuel to compress gas which you have to compress because you are using fuel...

Usually gasses like this are compressed (and liquified) via something like the Linde process:

https://en.wikipedia.org/wiki/Hampson%E2%80%93Linde_cycle

That is industrial scale and does not go onto anything that moves...

And you would need to store your compressed gasses somewhere too.

All of this is super complex, heavy, requires stupid amounts of energy and thus is way to costly to do on something that flies.