144 karma · joined February 20, 2020
Oil in some regions of the world literally seeps out of the ground (known as petroleum seep) and until the 19th century it wasn't really deemed to be something of value.
Recently because of panic buying of loo roll, there wasn't any loo roll available in the UK. On Amazon for a 12 pack of decent quality loo roll was selling at 4 times the price of what it would be normally and they became sold out.
You can lament about the ridiculous panic buying. However demand outstripped supply and the price reflected this. In normal circumstances they wouldn't have sold for these prices and people would have had to sell at the regular price.
It isn't about what I think. When people make purchases they will typically try to buy as cheaply as possible. If someone is looking to make a purchase they will typically go to whoever is offering it cheapest, if other people want to compete they will either have to offer it at the same price or cheaper.
Are you claiming this isn't true? Because I have witnessed it with my own eyes. I used to work in a Petrol Station we were ones of the cheapest places around and we had a lot of custom.
Other places that were more expensive were empty at the same time on the same days because they were more expensive. There is of course exceptions to this (Head and Shoulders Shampoo being the classic example) but they are outliers.
The same with a labour market. The market rate for a C# programmer is approximately £350-450 a day in the UK. More specialist development roles pay more e.g. Angular JS developers which are typically £500-750 a day (the last time I looked). There is less Angular JS developers that are available (low supply) so to attract talent companies that wish to hire need to raise the rate. However C# developers in the UK are much more common (higher supply) so companies won't pay those high prices.
Are you telling me this isn't happening? Because you can go to total jobs yourself and put C# developer Manchester and you will see difference in market rate yourself.
> beyond market settling times, what the delta between labor value and market value very likely indicates is some sort of mispricing in the market, often due to some external, malign manipulation (i.e., an application of force, or power). efficient markets should tend toward the labor value of production, that is, profits are minimized to that of idiosyncratic risk (like pandemics).
Not true. You are making several assumptions:
1) That there is abundance of said product (high supply).
2) People are wanting or needing to make a purchase.
3) That there isn't other competitors which have improved their processes or paying their employees less.
Number 2 being the most important IMO as everything else is normally equal. If nobody wants to buy it at the cost (or higher) you will be selling it at a loss.
The labour theory of value is simply describing the cost of producing something. Whether people are willing to buy it as that price (which would be same as selling it at cost) is an entirely different matter.
Sure a lot of developers abuse the feature but I fear this might create another set of problems.
The $10,000 bounty is about right for this sort of work. In fact it might be a little low, but I have no idea how OBS works internally so I could be completely wrong.
However the old "Learn C" and "Write a compiler" which are within meme territory tbh. It is more important generally to understand what a particular in whatever language you are using to know what the compiler / interpreter / run-time is doing under the hood as most developers will be working with a high level language.
I've seen a lot of "how to improve as a programmer" articles and IMO what seems to be left out is learning how to do things as simply as possible. Many of the software systems I've worked on is so over-engineered, many simple websites are huge both client and server side and they usually don't warrant it.
The 5th reason especially You can convert markdown into other formats such as PDF, Word, Media WIKI etc using pandoc (I am sure there are other programs). It is trivial to write a shell script or similar to convert markdown files into another format.
> After that, it is hard to migrate to another tool, as custom-defined HTML classes and flavor's features won't work outside the current set of tools and page designs.
That contradicts his Lack of Extensibility. Typically anything custom you do outside what is supported officially by the tools maintainer is your own lookout.
Markdown is a like a lot of things that succeed. It is good enough to produce well formatted documentation to be read by a client and simple enough for people to learn it relatively quickly without headaches.
I don't want to be rude but you are completely misunderstanding what CSS and HTML are supposed to do.
1) The <p> tag denotes that the content in the element is a paragraph in the document.
2) The styling is just tell the client (which is typically a browser) how the element is supposed to be styled. It isn't supposed to mean anything in relation to other elements and it isn't supposed to convey meaning.
Generally wherever possible you should try to separate the markup and its styling. You can't always do that, but you should try to.
https://www.youtube.com/watch?v=i9MXYZh1jcs
He gets into the explanation of how the tracker software works about 8min 30seconds in.
Typically though if you got a cracked game at that time it would have the crackers group name and there would be a little graphical demo and some tracker music.
Bootstrap does this on some components but it has loads of positional bits and pieces mixed. Also the components are fairly generic.
Yes a table will need to have the correct elements in the right order. This isn’t presentational it is semantic.
HTML5 does this better than HTML 4 as it has more semantic elements as a response to the more complicated layouts of modern web pages.
You are complaining about the wrong thing.
> Despite the popular claim to the contrary, HTML was always part of the presentation layer.
Not at all. It is document format. Designs that do not respect that doesn't change it's intrinsic nature.
This is like complaining that a shoe isn't a very good mallet.
If you look at other document writing system such as LaTeX. You will see that there are Sections, SubSections etc.
The link to the CSS simply told the browser how these should be presented. LaTeX has something similar as you can create a document class and Word has different styles you can import.
Having a concept of a document structure with a set of styles attached which you can change easily is a good idea.
The HTML document should make sense without a style sheet and if you write/generate semantic markup it does work properly.
Push notifications are becoming an irritation mainly because of their overuse. The number of sites where you go to them to have a look at one piece of information and you have to tell them no to push notifications is becoming quite an annoyance.
I really should write something on forgotten simpler CSS / JavaScript techniques.
It goes against what CSS was supposed to do and generally the results are IMO hard to work with because you have the overhead of having to learn how the framework works rather than just using the fundamental principles of what you are working with. Also the markup is horrendous to read.
With modern CSS you are given so much control. Your style-sheets aren't complicated anyway.
If you understand how the document flows, separate your CSS from your markup, write clean and valid markup and keep everything as minimal as possible. There is really a "zen" like element to it which I think is kinda lost today.
However when it comes to code I am a minimalist and tend to do as much as possible with Vanilla JS.
If the markup is done properly in the first place. It is incredibly easy to restyle and you typically don't to rework much markup. It just ends up working.
> but it allows much much faster development, less spaghetti styling, less cross-browser concerns and less code all around.
I have seen no evidence of this in practice. This is only true if you design is basically a skin of these frameworks. If you have anything remotely custom you end up overriding so much you might have well just started with a normalise/reset style-sheet. So for some internal application that never seen on the outside, you can use bootstrap and slap something together quick sure. However if you are actually building something with a unique it just doesn't really work.
If you think about what you are doing instead of just jumping in and coding. You can break stuff down properly without the need for hundreds of classes that typically come with these CSS frameworks. You do end up with clean CSS and the markup is clean and you do have less code.
By doing things properly i.e. you markup and css is correct. You have less cross browser bugs. I end up in my current being asked by a coworker to pick up IE bugs (yes we still support IE9 upwards). Only 10% of the fixes are actually problems with IE. 90% of the problems are correcting the markup (making it valid) and cleaning up the CSS and it just works cross browser. Sure you will have to work around things like you don't have flexbox and other niceties and you have to use an alternative style-sheet. But fixing the markup normally gets it from "not rendering properly at all" to "rendering only slightly wrong".
Also a lot of the things I wanted 5-10 years ago that I had to work around are now being included. For example there is a decent-ish http request API.
I don't like web assembly. I think it is actually worse in a lot of ways than the huge JS frameworks that people think that it will replace.
Though I will admit that I typically Brave, Brew, VSCode / Visual Studio and iTerm. It might be me just and not getting any of the real benefit, but I tend to use Windows and Linux just a shell.
I still use VB.NET for creating quick tooling for either myself or non-technical users. There doesn't appear to be anything else really these days for doing that. The newer options from Microsoft tend to enforce a lot of patterns, which just slow you down, when for small tools you don't really require all that guff.
I hope with an open source .NET compiler it will be possible VB.NET to carry on well beyond Microsoft's culling.
I am a .NET contractor/consultant at a similarly large corporation (just finishing a contract now). I wouldn't expect a penny from the corporation. It just how it goes.