dlsa

So the 32 bit code and the 64 bit code is equally inefficient in your opinion?

I noticed high and low in there so those code snippets look like 32 bit code, at least to me.

Is that even a fair comparison given the arm and x86 versions used as examples of "better" were 64 bit?

If we're really comparing 32 and 64 and complaining that 32 bit uses more instructions than 64, perhaps we should dig out the 4 bit processors and really sharpen the pitchforks. Alternatively, we could simply not. Comparing apples to oranges doesn't really help.

From the article:

Let's look at some examples of how Risc V underperforms.

First, addition of a double-word integer with carry-out:

add t0, a4, a6 // add low words

sltu t6, t0, a4 // compute carry-out from low add

add t1, a5, a7 // add hi words

sltu t2, t1, a5 // compute carry-out from high add

add t4, t1, t6 // add carry to low result

sltu t3, t4, t1 // compute carry out from the carry add

add t6, t2, t3 // combine carries

Same for 64-bit arm:

adds x12, x6, x10

adcs x13, x7, x11

Same for 64-bit x86:

add %r8, %rax

adc %r9, %rdx

Screeps is something we could invest far too many hours into.

That's what someone said about Cracktorio. I think we spent like 40 hours on the demo.

Not going to play this game. At all. I sense I could easily put 3000 hours into it. A man needs to know his limitations. Cracktorio taught me that.

I occasionally need to rent cars and the UIs are often so bad I just ignore them. Set them up at start and use a car mounted phone instead. Suction cup mounts to the rescue.

Navigation UX is usually just annoying in most cars anyway.

"Passenger" could just be a backpack full of stuff. Or a water bottle. One of those large water boxes with the tap on the front should do it as well.

The real kicker is that they're still other people's computers. There's definite benefits as well as costs. Ignoring either is not a good idea.

Centralisation into just a few large providers is another bad idea we're heading towards or have already arrived at.

Ironically I got told that you can be required to show immunisation certification to enter a hardware store. My thought-to-be-silly-to-make-a-point example about the hammer is reality right now.

Plenty of parallels but you won't get exact matches... yet a few things stand out.

I'd point at the war-on-terror as a good example of a permanent or equivalent always-at-war situation. Its not a stretch to suggest that a lot of the privacy and surveillance is based around anti-terrorism initiatives and plenty of security theater is now in place because of that. The war-on-drugs was another version of that. The war-on-... rhetoric in general is almost cliché now. This is not to say its not serious but consider the 1970s had quite a lot of terrorism going on. eg The UK had regular bombings from the IRA.

Political correctness tends to adjust definitions in ways very reminiscent of Double-speak. It seems to be a rich source of new words and terms. Like a conveyor belt.

The surveillance aspect is obvious.

Unfortunately the governments implementing these measures seem absolutely determined to treat Orwell's 1984 as a training or howto manual. As we descend further into authoritarianism, tracking and other privacy busting measures will become even more normalised and entrenched. You'll soon need to show identity and other papers to get into a shop to buy a hammer.

This kind of breach isn't possible in Australia since their laws can beat the laws of math. Countries with less powerful laws are apparently not so lucky.

https://www.gizmodo.com.au/2017/07/prime-minister-says-the-l...

(Yeah, tongue firmly in cheek. Laws of math oddly enough seem to work just fine for taxation, depreciation, etc etc)

You'd be correct.

I was asking the question to get a handle on base process pricing and experiences for a design currently utilising 500k LUTs and residing in a fpga. But I didn't want to get too bogged down in details.

Do you still recommend the 74LS30 for that?

Anyone familiar with ASICs? If I wanted a 8 x AND gate, what would that cost, ballpark figure? I'm just trying to get a handle on the costs and figure that might be a good measure.

Krita is working out very well for my pixel wrangling tasks. The people around me also appreciate the improvements in workflow compared to gimp and photoshop. I just can't go back now, they're both too clunky. Usual caveats apply: I'm not in a studio full of photoshop power users that demand standardisation. That's a big factor.

Also, I'm not a graphic design guy. But when I need layers of pixels and brushes and the rest of what I consider required tools, Krita is my tool of choice. Kind of like Blender for 3D, although we also use that for 2D now since the newest upgrades have gone through.

Explorative notes because this provoked some thoughts and opinions of my own.

1) Value them like a lottery ticket. Now what? They are worth nothing or something. You won't know until they are actually drawn in 4 years. Waiting is fun, right? You're happy to wait for your bonus?

2) Do you enjoy working there? Right now they are chains binding you to the business. Is that an issue? If you get bored and it becomes just a pay check, can you start a suitable side hustle so you stay awake?

3) They're worth nothing at all. The business goes bust in two years. What opportunity cost did you pay? What other actual paying positions did you pass up?

4) Is the business sane enough to last another 5 years? 6 years? Other than your salary, would you actually invest in the business if you could on the market? Are its fundamentals valid? Does it actually produce cash flow? It seems like it is progressing. You worm for them. Are they progressing in your perception? Could you convince me to invest? What would you say?

...but I only met her last night for a beer and dinner, you mean I have to set up an international group of companies to protect my stereo, fancy dining table and car? Yes, son. Otherwise you'll lose everything. Here's a list of firms that can help...

What a world we live in. I doubt nothing you wrote but the steps that lead to your understanding seem as difficult as my own. Society is truly a mess.

In plenty of places, you don't even want to live with someone too long without a pre-nuptial agreement and even then the law can cancel those agreements.

When the child support ends a lot of power the state grants women to tear apart a mans life also evaporates. There's a possibility of a silver lining when child support ends. Divorced men need to remember that. Often times its the very start of men resuming a relationship with the children they've been blocked from seeing for all those years.

If men comtemplating suicide could realise this and see it as the light at the end of the very dark tunnel then they might keep their faith in themselves and their future.

If you have much to do with family court you'd fully understand why suicide is a way out for men treated like sources of money with little other value.

It would be quite educational for all men to attend family court as an observer prior to marriage. They might reconsider marriage as an institution altogether. Society itself might have to realise how badly things are set up.

Maybe not. Everything's fine. Enjoy your special day. It'll be great.

Business should be fully aware that they are judged on the entire experience.

So, TJ's are fully responsible for the parking arrangement experience even though, as they say, they are just tenants and its their landlords who are imposing this. Those facts don't make up for the bad experience.

Its still TJ's fault and at that location they have bad parking. Its now up to them to fix their bad parking situation. If they can.

Others have pointed out the landlord could put in a turnstile and charge $1 per entry. Indirect methods, eg tracking apps, are the equivalent. Refer to the parking situation.

> This article assumes that you already know that that's what you need

This is how I read the article. It was about how to implement network protocols in elixir and here are two of them: redis and msgpack.

Having an elixir based redis server is not the same piece of the puzzle as having elixir simply talk to a redis server. For one, the elixir based redis server can have arbitrary rules around keys and values that are not supported by redis. (Same said for a redis server written in C or python or rust or...)

This approach lets you store all keys and values in a dict, b-tree, sqlite or postgres etc. Want to store each value in a flat file? Sure, now you can. Only you know if this is actually useful.

At least, this is how I made sense of this.

Never considered fast-math. I get the sense its useful but can create awkward and/or unexpected surprises. If I was to use it I'd have to have a verification test harness as part of some pipeline to comfirm no weirdness. Literally a bunch of example canary calculations to determine if fast-math will kill or harm some real use case.

Is this a sensible approach? What are others experiences around this? I've never bothered with this kind of optimisation and I now vaguely feel like I'm missing out.

I tend to use calculations for deterministic purposes rather than pure accuracy. 1+1=2.1 where the answer is stable and approximate is still better and more useful than 1+1=2.0 but where the answer is unstable. Eg because one of those is 0.9999999 and the precision triggers some edge case.

Its a shift in some ways. Lowers a lot of friction for prototyping and production purposes for plenty of adhoc tools. People think this will help. It does and it will. I've used quite a bit of it and had generally good results. We're only in the early stages even though plenty of tools are a decade old.

But it has limits like everything else. Vendor lock-in is returning similar to the old days of mainframes. But at least this time around the tools are more varied and from different vendors as well as the ability to use one of many languages in most cases.

You can run a bunch of businesses with writing very little code. What they don't seem to include in that no-code advertising blurb is the amount of configuration required for some no-code solutions. Especially integrating each *aaS to the next. That seems trivial but can become quite a project.

The bigger cloud offerings such as AWS create dependencies that might be an issue for a lot of businesses if they try to switch. This includes wanting on-premises solutions for whatever reason instead of the cloud. AWS is more than "hey you can run redis, mysql etc in the cloud". Its constellation of convenience is quite a thing to behold. Gets hard to leave. That's the new variant of the old vendor lock-in strategy: You don't want to leave and it can hurt a lot to do so.

There is also an issue with non-cloud alternatives as inherent to most of the no-code solutions in practical use. Unless of course you have a disaster recovery plan for when your favorite sites go down. We still need to have DR plans even for no-code.

You are ready for the no-code platforms you use to go offline, right?

Haven't mentioned security. Better not forget that either.

No-code means more contract management.

Compilers and interpreters need a new pass to detect these characters in code and treat them as hard errors. This doesn't stop their use in comments where presumably they are still ok.

Alternatively, there needs to be an uptake of the use of code linters and pretty printers.

A bit of both perhaps.

I'm still evaluating this myself but:

Alternatives exist in various ways https://news.ycombinator.com/item?id=28830640

I still like IRC but understand why its being left behind for plenty of purposes. Yet still useful for plenty more.

Nothing says "we love the planet" more than a mountain of old dongles, broken and cracked iphone charger cables, and unrepairable consumer electronics.

All of which could have had much longer useful lifetimes through the most basic engineering practices. Apple cables are perfect examples of style over substance. Insufficient reinforcement for a daily use item. Poor design.

Bumped into this while searching for blender and postgres. Who knew freshmeat had been resurrected in a new body?

I'm not affiliated in any way. Just a happy visitor.

I wonder how many people it takes to enable the production of one IC. From absolute raw materials to device ready to place into a product. Machines with parts made using other machines and so on. Including the parts and processes and people's experience operating across all of it.

It would be interesting to see this whole thing mapped out. It seems to me that this might be helpful in understanding which parts of this ecosystem might be low hanging fruit.