Re: And there is of course also lazarus/freepascal
202 posts • joined 17 Jun 2008
Branching and merging worked from the start. Tagging was replaced by branching even.
SVN doesn't internally administrate as finely divided though, which lessens merge performance in more extreme cases. But that is something different. In cases both sides have changes in the same lines it sometimes borks.
(but a good 3rd party three-way diff tool as Beyond compare can even resolve many of those)
Personally I think the time for 3rd party tools vendors was simply over and from the late nineties on, the market belonged to the big IT vendors that predatory priced development tools because they wanted to promote their "platform".
Another ten years later, open source would also start a significant dent.
Borland maybe should have aligned themselves with a Big One in that period.
I did need to get a new ATM card due to the magnets of an NMR apparatus. There was tray for keys and wallets near the door that I forgot in my hurry.
Usually it was fine, but occasionally (specially after servicing) a light imbalance could generate a card wiping field (and it was said to rip the keys from your trousers, but I never witnessed that).
p.s., hydrochloric acid on your ATM card is also not very good for it. Just light acid on the hand and touched the magnetic strip of card at one end, but the card was finito, the strip got some green tinges at the end where the acid touched and refused to work a few days later . All in the nineties when the ATMs only had a magnetic script of course.
Some of that is what I thought. "Easy Visa" is an easy to implement solution to clear some last hurdles, and also attract the students before they become "World Class Scientist" (the bit where you educate an hundred to find one nugget)
To cherry pick world class staff, primarily you need to give potential staff good salaries and somewhat secure prospects. World Class staff coming for multi year tenures don't mind visa that much, since they can be handled by the uni (or research institutions) bureau for that. And those know which points to pressure for the real good ones.
Easy visa is the methods to drag in reams of (usually /paying/) hopefuls into your education system to bolster the base, to partially fund it, and with hopefully some cream rising to the top eventually.
Well, indeed Apple has shown many signs that it takes users of software not serious, and focusses chiefly on media consumption. Primarily from its own services.
So the blame is on the Apple users still trying while the writing has been on the wall for a decade, while Apple is laughing all the way to the bank.
Indeed how long, and how about versioning? The problem with .NET is always that there is no single version default available on all targets. (and if win7 is pushing up daisies, it will probably be replaced by old corporate LTS versions of Windows 10)
If you need to deliver something simple like a tool to configure a piece of hardware then you are stuck with a runtime versioning mess with anything but the win32/64 subsystem.
I've been on an major (Chello) ISP helpdesk for two years, doing 2nd and 3rd line (senior) work. Basically all the customers wanted was an engineer to come and sort things out, and they all had already checked everything (they thought). NOT!
We already had expert systems for self help, and they were next to useless. (unless you liked in kicking in open doors). Customers simply couldn't specify the problem beyond "Internet doesn't work" (*)
(*) test one: does mail work? Yes, hmm, then "some internet works" :-)
In the late nineties, our computerclub had freebsd systems, multiusers systems off a shared NFS with the hardware also doubling as terminals.
To make emergency login to the physical console possible without logging of the locally logged on user, they simply defined extra getty's on up to 20 terminals (F1..F10 and iirc ctrl-shift-F1..F10). The ctrl-shift-Fx combos (and the extra terminals on them) were a bit a secret.
I was porting a full screen app, and experimenting with consoles in raw mode, and found a whole bunch of syscons ioctls. These included font manipulation. I also found out that if you execute a program with "exec xxx" on one of the hidden consoles, that the terminal stdinput handle remained valid for syscons ioctlrs and that the syscons didn't change the settings on a per console/getty basis.
I used that for two programs:
- one that created a lookup table for 2 x 26 characters (upper/lower) that shuffled the values. Then I set font and keyboard controller according to this table. So you would press the "E" key, and the "E" glyph was shown, but some other ascii code (like "v") was actually generated to the terminal.
- I took the VGA font and did some bit twiddling (shift upper and lower rowes) to make them a bit cursive or mirrored. Then I started animating the font. (so slanted to the right, normal slanted to the level, normal etc).
The program hooked sigusr2 which could be used (from a remotely logged in session) to turn these features on and off. Fun times, though in the end I didn't trick my main targets as badly since they had seen me develop it. We used it with a lot of fun next year on the new batch of students though.
Intel coined AVX512, and thus has to invest silicon surface that largely goes unused in the first generations to get a critical mass. IOW it is seeding it to get people to use it.
AMD doesn't, so only upgrades the vector unit when it actually becomes commonly used, and spends the surface one whatever is needed now (either making cheaper or other features)
Keep in mind that there is barely enduser -512 silicon out there atm, and worse the standard is hopelessly fragmented in substandards.
Some Xeon servers had some older substandard, but clock down when heavily used, or implement a 512 instruction using two 256 pipes (as AMD does for AVX2 currently in ryzen 2x00)
I don't remind version details any more, but the last one could be made to run quite long using LD_PRELOAD tricks (adding a runner script that set them). People kept them running way past 2010, and pretty much only the mobile wave made them reconsider.
I never really used it. I didn't need the commercial finishing touch for my internal use/server apps, and Free Pascal/Lazarus was more comfortable, and more importantly progressing and supported.
I still use Delphi though on Windows for my core applications, mostly because of more convenient debugging.
Small apps, utils and cmdline work (including a sizable part of the testing) all work with FPC/Lazarus.
Afaik the former serverside Linux option was based on the so called nextgen modification of the original dialect that is used on the mobile platform offerings. As it originates in the Mac world, it borrows heavily from Objective C and misses many original language features.
The original Kylix WAS a full dialect version, but I can't seem to find what this thing uses.
Delphi never generated much source (the control's properties are stored in resourcestreams). JBuilder is a better example of a two way source based designer.
Also, they had a slightly different screen model. Many modern tools assume a Browser layout model that quickly adds a scrollbar if things don't fit, rather than shrinking them to size.
That is indeed interesting. 32MB per chiplet. I haven't seen any details yet if Ryzen3000 is again an less efficient exclusion cache.
Also many image processing benchmark show great "3000" improvement, but be warned that AVX performance doubled since the "2000" series. Some benchmarks are biassed towards AVX, but if your workloads are not AVX wymmv.
In the end, it is probably still a wait till the embargoes on benchmarks are lifted. (and even then, selecting the benchmark that is relevant for you is an art (*))
(*) I usually go with the compiler benchmarks, since even though I"m in image processing, I found these benchmarks are closer to my applications real world performance, probably because my vision apps are not stuffed with whole image operations.
Depending on keyboard, they are verbose as braces require modifier keys to type. Textual delimiters, even not overlong multicharacter ones are actually easier and quicker to type, as they are two hand typed in the center of the keyboard.
The preference for braces only shows that programmers can count, but not know much about typing.
The Nazi SS used runederived characters for its SS notation, like U+16CB, not normal latin characters. As long as it is not an unicode domain, we're safe :-)
p.s. it might still be a good idea not to do it. Neo Nazis are not very literate, and the subtleties might be beyond them
I came back to an old company to do some updates to an old app and noticed the database password was still the same. After 6 years.
Application passwords should probably also be regularly rotated, and software should therefore never hardcode them.
An ex employee who breaches your network (like in the article), might be able to siphon off complete databases otherwise.
Biting the hand that feeds IT © 1998–2020