←back to thread

669 points danso | 1 comments | | HN request time: 0.379s | source
Show context
Hokusai ◴[] No.23262161[source]
> Basically, only Apple (and, more recently, Samsung) use the HEIC format — most other websites and platforms don’t support it. Even popular Silicon Valley-based services, such as Slack, don’t treat HEICs the same way as standard JPEGs.

This is the key part. Many in the software industry still believes that the start-up mindset of break things move fast applies to us. The economy depends on software, governments depend on software, education depends on software, lives depend on software ... but we treat software as a toy where a new fancy image format is a reasonable change to make because our platform gets a little more fancy and for sure a little less compatible to lock-in users.

I am all for regulation, and it is coming, as the software industry has shown to be an immature risk-taking mess. But, it can be a more bearable amount of regulation if we exercise some level of self-constraint on how we break each new release of software.

If we keep blaming traditional business (education, accounting, grocery stores, etc.) for not "updating fast enough" to new trends, they are going to justly react to our demands on their thin margin profits and ask the government to stop us. When you do not know if your business will survive another month, to have to invest non-stop in new software without any tangible benefit is an unreasonable demand.

Software has become too important the past twenty years. It is time that as a industry we realize that and act accordingly.

replies(7): >>23262214 #>>23262330 #>>23263653 #>>23263691 #>>23263900 #>>23264074 #>>23264368 #
cm2187 ◴[] No.23262330[source]
Plus the backend doesn't move fast. The .net framework only got a json serializer recently. I am not holding my breath for system.drawing to handle HEIC!
replies(3): >>23262608 #>>23262840 #>>23262893 #
MattGaiser ◴[] No.23262608[source]
> The .net framework only got a json serializer recently.

What do you mean by recently? I am not a .net user, but this seems quite basic.

replies(4): >>23262929 #>>23262996 #>>23263009 #>>23263045 #
1. foepys ◴[] No.23262996[source]
Early when JSON was new, people were using the JavaScript parser included in .NET to get the values. Then Microsoft build a small JSON parser for their ASP.NET library. But then James Newton-King build JSON.NET and Microsoft eventually switched a lot of their libraries over to it because it was just very good. It could do a lot of stuff very fast with a nice API.

Last year Microsoft introduced a new and more efficient way to allocate memory natively into .NET Core 2.0 (Span<T>). Since JSON.NET is still used by .NET Framework that doesn't support the new API, Microsoft created System.Text.Json that includes a new JSON parser that utilizes it. The first Microsoft project to use the new parser by default was ASP.NET Core 3.0.