sklogic

13 ms·

91.
by sklogic 10y ago
Still it might be suitable for a relatively cheap mid range FPGA, even Spartan6. EDIT: actually, no, it's a single lane PCIe3, such clock rates are well beyond the FPGA range. Pity.
92.
by sklogic 10y ago
Well, OSH Park and alike are surprisingly good now, I even had some success recently with an ice40lp WLCS16 package (by pushing well beyond the recommended design constraints), got 1 passable board out of 3. So even a very small ball pitch
93.
by sklogic 10y ago
Could not find anything on a ball pitch. Can it be suitable for DIY projects?
94.
by sklogic 10y ago
I was invovled a couple of times in bidding for the government contracts. Do not have proofs, of course, but the entire design of this system was very open for corruption.
95.
by sklogic 10y ago
It is indeed. Just take a look at the thoroughly corrupt and secretive process of awarding a train franchise.
96.
by sklogic 10y ago
Exactly. Programming is mathematics, all of it. It is not just overlaping with mathematics in few peculiar areas but it is nothing but mathematics and must be treated as such.
97.
by sklogic 10y ago
I see, I must have misinterpreted your intentions. In such a case verbosity and specialisation of an implementation may be helpful indeed.
98.
by sklogic 10y ago
There were countless attempts of replacing this notation with something more structured, with OpenMath [1] being probably the most advanced (and yet failed) take on this, as well as multiple CAS (Axiom, Macsyma, Mathematica and alike). But
99.
by sklogic 10y ago
> you agree that pseudocode is not code and flow charts are also not pseudocode What? I just demonstrated that pseudocode is an ultimate form of a code, flowcharts included (they're just a graphical pseudocode). Maybe you do not u
100.
by sklogic 10y ago
Symbols are nice. Code is awful: too verbose and obscure. So what's the point here?
101.
by sklogic 10y ago
I can only hope I will never have to work in a team with someone like you. That would definitely be a massive waste of time. A typical workflow based on a pseudocode is very simple and efficient: you solve your problem in a pseudocode - a
102.
by sklogic 10y ago
Yes they are. A formal language is a code. Any formal language. What is the difference between code and pseudocode in your opinion? And given that on a whiteboard interview you're writing a pseudocode, it is not any different from a ty
103.
by sklogic 10y ago
Flowcharts are code. Pseudocode is a code.
104.
by sklogic 10y ago
> Who on Earth writes code on a whiteboard? Like, seriously You know, professionals do this. Anyone who value time and quality. Hipsters may find it weird, but, well, they have decades to learn before they'll become professionals.
105.
by sklogic 10y ago
Gnome not cleaning up after itself is a silly issue indeed. And especially not worthy of modifying a 40 years old policy, with suggestions like this making it even more silly and more non-issue. A far more reasonable remedy to such a proble
106.
by sklogic 10y ago
> Users should be free to reboot as often as they want. Of course. But an init system should not be optimised for often reboots, since it's a marginal and unlikely scenario.
107.
by sklogic 10y ago
> after logout Not after "logout", but after terminal is detached. For whatever reason. There is no such a thing as "logout".
108.
by sklogic 10y ago
You should not reboot that often anyway.
109.
by sklogic 10y ago
Why should we even talk to them? They're invaders. They must be exterminated.
110.
by sklogic 10y ago
> Breaking with historical behavior is called progress. Progress is building upon the best practices of the past, not breaking things because a bunch of very low quality, uneducated "developers" who all came from an alien cultu
111.
by sklogic 10y ago
> killing user processes after logout is totally reasonable How is it so? I cannot see a single legitimate justification for such a stupid behaviour. > "session" scope Exactly. There is no such a thing, and it should not e
112.
by sklogic 10y ago
Do we even need those low quality, low value "desktop" users? Why should everyone else suffer in order to make things tiny bit easier for an average Joe? Systemd is ill-designed throughout, and all of its design decisions do not
113.
by sklogic 10y ago
> most users don't expect lingering process after logout Who should ever care about the opinion of the non-contributing, useless users coming from the irrelevant platforms?
114.
by sklogic 10y ago
Process persistence is not an issue, it's a feature . "Desktop" users with their silly "issues" should go somewhere else and leave Unix alone.
115.
by sklogic 10y ago
> Who's "we"? We as an industry in general. > Low-level has changed significantly in meaning Not that much, actually, just shifted to the other domains. > but no one's going to do direct register writes. You&#x
116.
by sklogic 10y ago
It won't happen all at once. There will be a long process of elimination of more and more layers, leaving more and more developers available for the work on the less automatable (more fuzzy and chaotic) side of spectrum. It will take y
117.
by sklogic 10y ago
> be wary of genius developers. Is not it a subset of "high performers"? The dirty secret of all such "genius developers" is exactly this - they all simply traded rigour and quality for a speedy spitting out of a &quo
118.
by sklogic 10y ago
> Someone missed out on the early PC days I ignored PCs altogether. They were useless toys back then. We had SGIs, so who cared about PCs? > devs often reached below the abstraction, manually twiddling registers in the hardware And we
119.
by sklogic 10y ago
There was also this project: https://www.usenix.org/conference/dsl-99/verischemelog-veril...
120.
by sklogic 10y ago
You can do it as a hobby, yes. But if it is your job, you'll still have to navigate your way through impenetrable piles of convoluted needless layers. Not to mention the awful closed-source toolchains.

More ›