ErunamoJAZZ

Cool, just in time for the maintenance contract in the old legacy project I worked on like 10 years ago.

Similar situation here. I have been avoiding Instagram for many years, but I will not create an account for that hell right now just to sniff in Threads.

I wanted to use this linter, but they don't support many things that are used in real production code. By example, a simple postgres function like this one can't be parsed:

  CREATE OR REPLACE FUNCTION public.setof_test()
   RETURNS SETOF text
   LANGUAGE sql
   STABLE STRICT
  AS $function$
    select unnest(array['hi', 'test'])
  $function$
  ;

I have been using Postgraphile (similar to this one but for GraphQL) for many months. The great thing about this way to create systems is that you don't expend time doing glue code, just in the real business logic. But a big pain is to maintain your database code, by example the version control of your functions. There are not suitable linters, and testing can't be done over postgres functions but must be done over GraphQL instead. Using things like this will save you months of development time!, Even if I agree there are some systems that will not be good idea to implement in this way.

Failure rate is usually high early in the time, low in middle, and high again at long term. In the context of hardware, this mean that at start laptops will fail soon (caught in factory), or it will fail later in the time. A 10 years old laptop have a high probability to fail, so the probability that someone wanted to run a memtest is very high too.

yeah, but no one could run memtest in a young laptop.

Page never end to load.