That’s chemically not correct in and of itself, but I do wonder if through the process they are effectively creating a hydrocarbon by freeing the oxygen from the carbohydrate to create this magic non-adhesive adhesive.
Carbohydrates are oxidized hydrocarbons and hydrocarbons are reduced carbohydrates.
They can be and they are interconverted, both in living beings and in the industry.
In paper, most of the wood components except cellulose have been removed, so paper usually consists mostly of carbohydrates.
In general any adhesive is neither a hydrocarbon nor a carbohydrate, but a derivative of them. Natural adhesives are usually derived either from proteins, e.g. various kinds of animal glues, or from starch or from various kinds of gums or of resins or of latex.
Bitumen has been used as an adhesive that consists mostly of hydrocarbons, but it also includes some oxidized components that provide most of the adhesion, as pure hydrocarbons have lubricating properties, not adhesive properties.
I started with FreeCAD a couple of weeks ago. Parametric modeling is pretty hard and a couple of things are pretty hard to understand (no easy reuse of sketches between parts for one, one cannot extrude a binder is another one).
However, without it fine-tuning models for technical use would be untenable.
I definitely don't want to say that it's easy, but it's not terribly difficult. Does take a shift in thinking though, but then it clicks.
For reusing sketches, you can. There's external geometry and subshapebuilder. Doing assembly can be a bit tricky at first.
I'll admit, FreeCAD is a bit tricky if you're coming over from something more professional like SolidWorks or CATIA but it does get the job done and you can't beat the price. It's also really improved over the last two years
The issue of creating a DB wrapper doesn't go away by using an ORM. One of the complaints about ORMs I have, in practice, is people often create another wrapper around it.
I saw that a lot, too. I remember one project using Hibernate where the people involved decided to keep the Hibernate objects "pure" and then had them all wrapped in another object they used to keep information that didn't go into the database.
The whole project must have had 3x the number of classes that the actual complexity required, and keeping it all straight was something of a headache. As was onboarding new people, who always struggled with Hibernate.
It is not, it is related to both major phone service providers in my country. Abroad, everything worked just fine. And just in 4G/5G, however 3G is getting phased out, so if I forced it, I was often unreachable.
I was wondering if I could fix it myself, but I'm not even sure if this is firmware or OS issue. I assume the former, which afaik is not opensource? Not sure.
You should know the trade-offs of different algorithms, though. Many libraries let you choose the implementation for a spcific problem. For instance tree vs. hash map where you trade memory for speed.
reply