Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment: Oh no, there goes the neighborhood (Score 3, Interesting) 161

by Masa (#37066444) Attached to: Google Adds Games To Google+

Why in the hell they want to ruin Google+? I hate Facebook for two reasons:

1) It is annoying as hell to have those game requests. And if you don't block all applications, then you have to "enjoy" the constant stream of shit, when your friends request new tools in Farmville or want to share a pony.

2) Gaming becomes a sole purpose for using social networking site. Most of my friends don't bother to use Facebook for keeping touch or sharing interesting news or stories. They just spend time playing and filling their page with useless game-related crap.

I lost hope with Facebook long ago and recently joined Google+ hoping that it would be different. It seems I was wrong :(

Comment: What a fucked up move (Score 5, Interesting) 211

by Masa (#30961044) Attached to: Fertilizer Dump Spoils Intel's Pure Water
Why they even bother salting roads when there is -12 degrees Celsius? Salting is only sensible when there is about -4 degrees (at least that is a rule of thumb here in Finland). Also, using fertilizers is so completely boneheaded move because that's plain and simple polluting. I guess that someone made a risk analysis and decided that polluting groundwater supplies causes less deaths than icy roads. But I can't help but wonder what the long-term effects are for environment and groundwater.

Comment: Re:About forking (Score 3, Interesting) 470

by Masa (#28081609) Attached to: Wine Project Frustration and Forking

People might not like you taking their code and you risk alienating valuable assets if you proceed rashly.

So it is not socially acceptable to just fork the code?

I can understand the aspect of upsetting people and alienating the community, but the whole concept of "people might not like taking their code" confuses me here. I have always assumed that when something has been released under open source license, that act in itself is some kind of agreement that the code can be forked at some stage.

Personally I have never forked anything, but I have released few pieces of code to public and I have always assumed that if someone likes my work and wants to take it and improve it or take it to some new direction, then by all means, just take the code and start a new project. Granted, I don't have a thriving community behind me, so there isn't this social aspect to consider.

It's interesting to see that there can be this whole social protocol around the open source software development world. For me this is interesting, because I have always assumed that programmers in general seem to swear on following the OS licence literally regardless on social impact.

Comment: About forking (Score 4, Insightful) 470

by Masa (#28080629) Attached to: Wine Project Frustration and Forking
Not necessarily commenting this particular case, just wondering in general...

Why is it that when someone is pondering on forking a project, quite often we see these questions asked? Is the OSS community so polite that we have to ask permission from peers to fork a project? Why not just fork it and see, if the project takes off? Or is it about insecurity? Are we just afraid of negative feedback from anti-forking people?

Comment: Re:Sad day (Score 1) 240

by Masa (#27903103) Attached to: R.I.P. MS-DEBUG 1981 - 2009

er...when commodore 64's were popular there were no "old" pc's. the first ibm pc went on sale in 1981, and the C64 in 1982. clones did appear fairly quickly, but they were by no means cheap, and certainly cost more than a new c64, so the likelihood of getting one free (unless you mean in the "off the back of a truck" sense) seems dubious.

It was 1989 when I got the PC. And yes, the C64 was very popular in Finland at that time (another popular system for home use was Amiga). It was a Nokia MikroMikko, which was mainly used at banking systems. This PC in question was from a construction company, which was upgrading to newer machines (to 30386, if I remember correctly). They had to get rid of these old ones, so they gave them to the employees. This is how I got the PC.

Comment: Sad day (Score 4, Interesting) 240

by Masa (#27880441) Attached to: R.I.P. MS-DEBUG 1981 - 2009
So much fond memories...

The Debug.exe was actually my first contact to programming and the first language I learned, was x86 assembler.

It was MS-DOS 2.xx and all my friends played with C64s and coded all kinds of cool things. My parents couldn't afford a C64 but they somehow got an old PC free. Demoscene was a new and hot thing in those days and me and my friend programmed our first demo completely using the Debug.exe. Merging the two code-bases was an interesting task, when all you had was two pieces of binary and some unused memory space for copy 'n' paste. The demo actually was quite cool. Unfortunately I have lost my only copy.

If imprinted foil seal under cap is broken or missing when purchased, do not use.

Working...