dhab

ok, but isn't this a fire hazard?

unpaid one

Why would you be the best choice to become a Finn for 90 days?

thanks for pointing this out. For a while i had an uneasy feeling about this, and they way you have put it gives words to those: digital assets that we create and are licensed really can't be passed on generationally. Taking it to an extreme - imagine not having physical transcripts of historic documents - e.g. the constitution - and its effect on a country's trajectory (not that constitution would stay always relevant in it's original form - but still)

also maybe some creative work needs to be coupled with narratives, if intended for others.

For the example above, one could look at it as a meaningless blob, and someone else could describe it as a run-time behavior with y-axis representing time. Someone else could have some other interpretation. So a narrative could help it fit it in the intended place

how pragmatic is algebra driven design in the real world? Real world are full of exceptions, and I am doubtful those can be modelled with any kind of algebra.

> In order to properly compare the languages, we needed to collect the energy consumed by a single execution of a specific solution.

With this, Java ranking on top 5 is quite impressive. Considering that JIT optimisations wouldn't have really kicked in. My hypothesis is that if the Java program was allowed to run a few more times, and then compared, it would rank higher.

And, along the lines, couldn't the other compiled languages and vm-based (common lisp, racket) be JIT optimised?

A related question: Can a president pre-emptively pardon himself? I think there was some deal being worked on Jeff Epstein's case where that could have happened.

protomolecule is winning, as expected

Is there a fast.ai like library that allows a novice to try GPT-3?

https://github.com/openai/gpt-3 only contains dataset

Thank you - I found the article helpful in giving me a lay of the land

Thank you for your detailed insight

The post [1] (though old) - hints at no good libs for json (mentions a workaround for one he picks)

  > For me, the most important quality 
  I need in a JSON library is an unambiguous, 
  one-to-one mapping of types. For example: some libraries 
  will deserialize JSON arrays as Lisp lists, 
  and JSON true/false as t/nil. But this means [] and false
  both deserialize to nil, so you can't reliably round trip anything! 

Although this post is from 2018, wondering if it has improved since then.

[1] https://stevelosh.com/blog/2018/08/a-road-to-common-lisp/#s4...

Thank you for your responses. I was interested in learning about these concerns for Common Lisp only, and not the other dialects including scheme, clojure, racket ...

Unfortunately, PG's post is orthogonal to what I am trying to find. My concerns are mostly around community and operational aspects AFTER adopting lisp

On weekends: laying pavers in my front lawn :) During week (between work): learning lisp

i think the word "miss" is raising/idolising his personality. I didn't know Steve, but based on what I have been exposed to about him, he was a person I would dislike a lot, but, how he appears to have shaped some products is impressive. It's hard to tell if it was he genius, or if he was lucky or combination of both along with other factors, however seems he had the required chops.

I think we should not conflate people's perceived excellence in work life with their personality, and extrapolate "success" to mean they were also great personalities. I don't miss Steve, and hope someone/something knocks Apple to their senses to stop abusing (over-charging).

Everyone's spying - US, China, Europe, Middle East, East. Some are lesser known to detain and try in secret courts (USA), others are known to do that rampantly (china)

The ".com" tld, along with no licensing information on github does't make me feel very good about the request for contribution.

By that argument, we would have to boycott everything anyone with a disease ever touches - hard surfaces (virus is known to survive for up to a week) such as train rails would be tricky one - since we would have to send it back to the manufacturers with every suspicious contact?

I think cash has been known as dirty for a while now. There are ways to manage infection, without boycotting i think - with things such as washing hands frequently being sufficient in many cases.

"No evidence of that" is a valid argument.

I found most of the comment fine except for the part

  ...brothers and sisters

which feels like it was designed to evoke some emotion/strong response. I assume most of us would prefer them (brothers and sisters) be there, tucked away from the vicinity of family members?

The speaker claims that the cookie/key can be known by causing VM crash, which is done by exploiting the monotonic nature of cookie values which are stored as atoms which has a fixed cap on how many they can be, which when exceeded causes VM to crash. He estimates the time to do that be 10 mins (I forgot the exact memory limit)

Elixir, which runs on the Beam VM, had piqued my interest for a while, so finally set out to learn about it this weekend. On searching for "flaws" of the language and the platform, I (accidentally) ran into: https://www.youtube.com/watch?v=42k70Y-yTYY . (year 2017)

Video description:

  ...What many developers don’t understand is that Erlang is 
  built on an architecture and within ecosystem 
  that contains many subtle security flaws. 
  One such set of flaws allows anyone with the ability to 
  interact with a remote Erlang node to compromise 
  that node by abusing the underlying BEAM Virtual Machine 
  and the services required to run Erlang...

My notes:

* Looks like a deep issue in VM architecture

* It's not detectable at all

* Ericsson was informed 1 year prior to the talk, and their recommendation is to not expose nodes publicly

Speakers argument: Yes, but the threat still exists for another internal project to exploit it

* Speaker's belief: It doesn't look like it is going to be fixed (any time soon)

To me to me this sounds like a very serious issue - to the point that I have crossed off anything on Beam that - I wouldn't build/learn to build on, wouldn't trust (note: didn't say wouldn't use) another software that was built on it.

Overall, it seemed like a great platform that scaled upto a certain point with good guarantees on latency and throughput and resource utlitization. Not to mention, seems like (probably) only one platform that does pre-emptive scheduling. Heartbroken that after being marketed as "battle tested", this aspect of the VM/lang has gone under radar for so long.

I am not sure about other languages, but I have been programming in Java for many years, and Typescript does what Java does (minus performance on a long running VM on CPU bound computations) at a rate that I assume should be sufficient for most (business) apps, without any bloat.

Can you elaborate on promise fatigue. In our setup we use async/await and the latest ES (although most of us prefer not using decorators if we don't have to - only used it with mobx for UI code) bundled through webpack.

I am not sure what you mean by poor eco-system either. Both JS and TS (increasingly), I feel like is the second best eco-system (in terms of libraries and tooling) after a mainstream language like Java.

There are some warts I think in JS (around numbers, stream handling in pipes), but I think very few languages don't, and it depends on how likely you would be fiddling in those areas.

Extra tax on build pipeline cannot be escaped for anything with any complexity.

I feel like anyone who can write a complex app in good js, refactoring along the way at good speed, and meeting deadlines along the way and not introducing too many regressions, and come back and maintain it after a 6 month context switch, either has way too much time on his hands and/or works too many hours, or is much more smarter than I am and has it figured out.

I agree that there is some learning experience, but I am not sure how valuable that is. My experience working at a startup has been a learning experience on how not to do things (tech) and how wrong management feels - but I actually find that a universal experience within all companies - only in a startup it's more amplified. Theoretically, it might be valuable to know how not to do things, but that's only a small slice in an infinity of options. For the how to actually do things, I think anyone involved in trying to figure that out too - and feel like luck plays a big part.

My thought on this is, life-style business rather funded startup might be better in coming close to big company pay and independence - although myself, I haven't tried that.

Like Oracle.

This article proposes raising levels of NAD to counter aging related dna damage.

My google search also resulted in: https://medicalxpress.com/news/2016-12-pathway-linked-slower...

TLDR; NAD+ over-activeness is associated with a deadly form of brain cancer, and the article ends with an open question from an expert if it could be modulated to not have this adverse effect.

The next step is probably figuring out the tricky balance between these two ends.

In my experience having lived in 3 countries (5 years each), where tipping was implied good etiquette the most only in the US, and partly in Canada; by the rough measure of filling water or checking on folks and things of that sort, US isn't any better or worse than the other countries. In fact, I was actually told by someone in the US told me they employ strategies of being friendly and spend a few minutes conversing with patrons as they present the bill, so that they can drive the tip up (for good reasons - since they depend on them quite a bit).

Where I am living currently, I think there is more income equality - partly I believe is because of having more or less good wages despite line of work, and you get treated like how someone would normally treat you without being forced upon with the expectation of a tip.

For fault-tolerance in case the box is unresponsive for whatever reason, I think you would have to have a network behind a load balancer. So the issue of network latency still exists, but probably to a lesser extent?

My limited understanding of erlang/elixir is that it helps easily run actor model programs (fail-safe loosely defined as something with retries built-in) in a grid of long-running interconnected instances. With more and more focus on "serverless" development that I am being exposed to, I am curious to know if it is a good fit in this space. Say if you are constrained to use AWS serverless solutions - sqs, sns, dynamodb, lambda, cognito, api-gateway ... etc, with event-sourcing (for event-drivenness) with retries (automatic/configurable), (why) would using erlang/elixir vs say nodejs/typescript/go/haskell/java be a good choice (let's assume you equally love these languages for the sake of not getting in to 'but X is better than lang Y')?