jarjarbinks455

Yeah I think HTML is a good exams of a domain spec language. Instead of putting HTML in a dead string it can be in a parsible lisp object can be manipulated with editor commands. Of course you can do the opposite and have HTML file with lisp code embedded. Ie like a jsp in Java. But with lisp all this is at your finger tips. You don't need to wait for a big billionaire company to make html syntax for you. Or unit test supported at the language level. Or whatever

To me it is clear he is saying dry wall work and bridge design are separate skill sets. Contrasting that with the general term "developers" where different skill sets fall under one umbrella term.

I personally don't prep for doomsday events. But I think being financially stable, owning a plot of land, etc has advantages. Just normal things stable people tend to do or own.

Many people over extend themselves and will collapse with the economy.

Business Intelligence. Making reports. Usually over a large set of data. A normal query would be too slow so the results are pre calculated. Maybe you will calculate the average and total sales per city then dump the results into a table. From there you can quickly generate more granular reports like sales per state.

Yes. Originally it was a thought experiment. Just like mathematicians can imagine an idea and use a notation without creating a compiler.

You are also contributing to global warming. It takes a energy to transfer this data all over the world. And poor people will will run out of their monthly phone data limit.

Muscles (ie meat) are organs too.

I'm an omnivore. Chicken, eggs, beef, broccoli, carrots, peas, potatoes, rice, bread, cereal, milk, water, black coffee. Just about anything but this is what comes to mind.

Avoid deserts and sugary drinks.

Exercise is weight lifting. Focus on explosive lifts with lots of rest between sets to avoid lactic acid.

Well the point of gc is to allow the algorithm to focus on the problem domain. and not worry about mechanical implementation details of a computer. Everything has a trade off. An obvious win still must pay a cost elsewhere. In the case of GC it's simply not a good trade off for many resources. Sometimes it cannot be used even if you were willing to accept a trade.

In c# you can implement IDisposable. The garbage collector will call a dispose method allowing you piggyback on the garbage collector for just about anything.

But it's rarely a good idea to piggyback. Most resources are much more limited or time sensitive than memory. So you should free them immediately.

Even when your resource -is- memory it sometimes is a very very very bad idea to free via garbage collection.

Get ear cancer from the stronger radiation levels.

The secret of lisp is it's an abstract syntax tree (AST). When you compile a C or Java program it is first converted to an AST. With lisp you are already there. It's kind of a big deal and amazing it was invented in the 1950's. It's hard to "get it" without guided hand holding and a lot of deep thinking.

The structured nature of the code allows structured edits. Via tools like lispy. These ideas are floated for other languages but never get implemented due to difficulty and it's not an itch most people have.

Coding is against a live image. This allows really nice workflows. Other language users consider it an anti feature or incorrectly assume that means you can't use source control or do a full rebuild.

There tons of little niceties with lisp that add up to a sum greater than the parts. But the AST is the big one that no one understands.

If the goal is access to a wider job market then learn regular Java. It's the most popular JVM lang now and likely to remain so for decades.

The creator of c++ has similar thoughts about how c++ usage for Google search reduces co2 emissions. It's significant reduction. Reduces as much as a while city may produce.

The usual basics are hard to beat. Error logs to pinpoint the location of a bug. Info logs too to observe data or possibly timing issues with multiple users or things. And of course source control. After you know where in the code the error is you can use the blame or annotate features to observe changes in that area of code. Branch or tag at release points so you can apply fixes to the production version of the code without pollution of in-dev features.

No it's EQ. It's the latest BS thrown around by soccer mom's to describe themselves or their children.