News for hackers. Stuff that matters.

speleo_engr

Re:The Edge of Emulation on Wednesday January 22, 2020 @03:17PM (#22121549)
That sounds like a great idea, but you today we can't even synthesize arbitrary VHDL/Verilog code efficiently. The author needs an understanding of hardware architecture to write something that synthesizes versus just a test harness not intended to be synthesized.
Re:OpenVMS: state of the x86 port on Tuesday October 15, 2019 @05:39PM (#21264154)
I don't think its going to get any design starts, nor is that the intent. There are companies with rock solid legacy applications that want to continue to run them on newer hardware. VMS first ran on the VAX (long dead), then Alpha (dead), and finally Itanium (recently dead). x86 will let these legacy apps run for a few more decades.
Re:The Tragedy of UCS-2 on Saturday August 03, 2019 @02:05PM (#20601745)
Those are all shaping (and bidi) issues though, independent from encoding. UCS-4 is a single Unicode code point and the simplest encoding. Shaping may combine code points many to one, one to many, have ordering issues, etc. I think it is important for people to understand how shaping works and the code point/glyph distinction. Trying to duplicate the effort of the shaper when processing strings UCS-4 is going to lead to a world of hurt. Even English text with strings like "1/4" and ligatures in the font may display as a single glyph (that's font specific shaping, not encoding).

I've heard more than one person tell me they don't need to worry about text shaping since they are using UTF-8. (That statement doesn't make any sense) There is a lot of confusion with Unicode text rendering stack.

Re:Falsehoods programmers believe about Unix time on Wednesday May 15, 2019 @02:42PM (#19922423)
I read articles like this and come to the conclusion that UTC is flawed, not Unix time. Leap seconds seem mostly useless. People seem to think they are important for astronomy, but for every astronomical calculation I have ever done, your first step is converting from UTC to TAI. Move any jumps in time to once a century (or millennium). Such jumps have occurred in the past (Julian to Gregorian) and are easy to handle programmatically. People think time increases monotonically and it's confusing to push it any other way.

The idea that I don't know how many UTC seconds will pass between now and May 15, 2022 0:00:00 is absurd. The fact that a clock sometimes reads 23:59:60 is also absurd, as is the "possibility" of a 23:59:59 being a forbidden time on a certain date if we ever add a leap second of the opposite sign.

Depends on the company size and how long they have been around. Based on experience, I will always ask the following at a smaller company:

Have you ever been close to missing payroll?

Depending on the answer, make sure to find out when was the last time they missed.

It is very stressful to work at a place that has cash flow issues. They may very well be honest that they are on the cusp of big deals and/or funding. But wouldn't you want to know if there are short term issues before you start?

Re:Using Fourier Transforms to Multiply Numbers on Thursday January 10, 2019 @05:50PM (#18879190)
If you come at it from an engineering approach (e.g., electrical engineer), it doesn't look like that at all. In fact, the focus is on filters and spectral analysis. It looked something like this when I was at Georgia Tech:

First, you learn about the convolution operation that, given any input function x(t), get the output of any linear time-invariant circuit as y(t). The convolution integral is nasty, professors make you feel the pain a bit. Then introduce the Laplace transform to make the computation much easier. Then go to continuous time, continuous frequency Fourier transform. Talk about frequency domain a bunch, learn filter topologies, etc. Circuits class over.

Now comes a signal processing class where you learn about discrete-time signals. First, talk lots about sampling. Then, get introduced discrete time convolution. Now, learn the z-transform and the discrete time Fourier transform (DTFT) for a discrete-time, continuous frequency signal. Mostly discuss filtering and spectral analysis. Intro to signal processing class over.

Learn about sampling the DTFT in the frequency domain. This is the DFT, which is usually presented as a sum that would require O(n^2) operations to compute. Learn that this corresponds to circular convolution and learn about zero padding for traditional convolution. Finally, get presented with Cooley-Tukey FFT algorithm for base-2. Focus is still signal and spectral analysis. Talk lots about windowing. You may get a mention that convolution corresponds to polynomial multiplication here. Or maybe they talk about grade-school multiplication, its really the same thing as polynomial multiplication with a carry. Senior level signal processing class over.

Re:Globally, Almost Four Out of Ten Music Consumers Are Pirates on Wednesday October 10, 2018 @03:01PM (#18187884)
How is vinyl more durable as far as physical media goes than a CD (digital format)? Vinyl can easily warp when improperly stored, degrades every time it is played, and even a small scratch result in audible imperfections. A CD at least can be scratched heavily and still be identical to the original thanks to forward error correction by Reed-Solomon codes.
Re:Dumb Things Camera Companies are Still Doing on Wednesday September 27, 2017 @10:18AM (#15347992)
If Android is on a camera, I want some sort of a hypervisor situation where it does not interfere with real-time operations. My Canon T4i will very responsively snap a picture once I have locked the focus, aperture, and shutter speed. I do not want to lose that and "gain" lagdroid.
Re:Nuclear deterrence is limited by geography on Monday September 25, 2017 @07:26AM (#15329524)
Nuclear deterrence has been a controversial topic for 50 years. There have always been arguments for nuclear disarmament instead.

I took the point of this article to be that the ICBM portion of the US triad does not work on NK since a missile must overfly China or Russia.

I personally don't think there is much risk of war with NK. NK has everything to lose and nothing to gain by starting any sort of war.

Re:Terminal and shell performance on Tuesday July 18, 2017 @08:04PM (#14801088)
Triple buffering confusingly means different things. Both you and the OP are correct. The OP meant something in line with what Wikipedia says: https://en.wikipedia.org/wiki/Multiple_buffering#Triple_buff...

"In triple buffering the program has two back buffers and can immediately start drawing in the one that is not involved in such copying. The third buffer, the front buffer, is read by the graphics card to display the image on the monitor. Once the image has been sent to the monitor, the front buffer is flipped with (or copied from) the back buffer holding the most recent complete image. Since one of the back buffers is always complete, the graphics card never has to wait for the software to complete. Consequently, the software and the graphics card are completely independent and can run at their own pace. Finally, the displayed image was started without waiting for synchronization and thus with minimum lag.[1]

Due to the software algorithm not having to poll the graphics hardware for monitor refresh events, the algorithm is free to run as fast as possible. This can mean that several drawings that are never displayed are written to the back buffers. Nvidia has implemented this method under the name "Fast sync"."

Re:John Carmack Archive – Interviews [pdf] on Friday June 30, 2017 @01:18AM (#14668775)
BSPs weren't new to the Quake engine (Doom had them). Gouraud shading, lighting, and TCP/IP multiplayer are what made Quake revolutionary for the PC. These things existed on SGIs costing $100k for years before too. The optimizations to make this on a PC is why Carmack is genius.
Re:Iosevka – A Typeface for Code, from Code on Saturday April 01, 2017 @09:19AM (#14011963)
Monospaced fonts simply mean that the horizontal width is constant. While this also means there aren't any kerning pairs, it is a different concept. Simply disabling kerning does not mean a font is monospaced.

Kerning is a table of pairs that allows them to have more aggressive advance values. For example, with a sequential 'V' and 'A', the 'A' could be moved closer to the 'V'. But kerning doesn't have anything to do with the fact that in a variable width font that 'I' is narrower than 'X'.

Re:RISC instruction sets I have known and disliked on Sunday May 01, 2016 @02:56PM (#11607394)
"If you do have the misfortune to have to work with SPARC"

So true... I work with the LEON (GPL implementation of SPARC) and have the occasional very bad day of SPARC asm code.

Those are good. The only one I have worth mentioning was a conversation that went like this:

Manager: So you like caving?

Me: Yeah, I was able to go on a month long expedition last summer to the mountains of Peru.

Manager: I can't believe your old job didn't fire you for taking a month off.

Me: I gave a lot of notice and had the vacation saved up.

Manager: That would never happen here. I have a problem leaving for a week.

In retrospect, I really appreciated the honesty. Declined that offer without hesitation.