You mention being comfortable in java, but you also say (essentially) that you don't know a thing about client side coding. You mention WebObjects, which is rare, and I imagine most folks don't have a clue what that is. But you don't mention MVC, which seems odd to me.
You're going to write a new app using 2-4 new frameworks. As far as I'm concerned, frameworks are more work to learn than a new language.
As someone who enjoyed WO in the Obj-C days and suffered through it in the Java days, here's my advice:
Go with Ruby on Rails. Ruby is a fun language. Rails is a reasonable framework. On the client you could do a lot worse than jQuery, twitter bootstrap, and maybe Ember.js or backbone for the fancy stuff. I think that starting out with ember/backbone will give you a leg up when you make the move to non-web mobile platforms. Oh, and I do recommend coffeescript - it feels a lot saner to an OO developer than raw javascript.
Prop 13 is why people who bought their homes when they were $75K (or less) can still afford to live in them now that they're worth $1M+(or much more) and they're living on retirement.
In other words, Prop 13 protects millionaires.
I forgot, why do we need to protect millionaires? Why can't they take their windfall profits and move into less expensive accommodations?
You're a bit flamey, but I'll bite.
I believe that a home is not the same as a house. You should not be forced to move out of your home just because the houses in your neighborhood got bought up by rich folks.
I don't believe you're $ rich because your home is worth a lot. I don't think of a home as a liquid asset.
I do believe in a strong inheritance tax. So I guess I believe in protecting people's homes until they die. And I think that's going to be hard on the kids who grew up in the house if they can't afford the taxes, but that's where *I* would draw the line...
... But the law is so badly written that it has allowed some corporations (which don't have to worry about dying) to use shell games to conceal their continued ownership of a property even after they sell it, allowing them to reap the profits while keeping property taxes low for the new buyer. (How do you track down the ownership of a property when it's owned by some kind of huge conglomerate or partnership?)... We seem to be stuck with it.
Ownership is easy. It's the name on the deed. The owner should not be protected from raising taxes on commercial property. It really doesn't matter where the shells are - as long as the owner gets taxed. They'll pass the costs up and down as they can.
Prop 13 is why people who bought their homes when they were $75K (or less) can still afford to live in them now that they're worth $1M+(or much more) and they're living on retirement. I'm a big fan of rolling back prop 13 protection for businesses, which I think SHOULD need to keep up economically with their neighbors.
But toward the partent poster's point that we elect these folks to govern and not just tally their constituent's opinions, I sure agree.
1) Be available when you're suppose to: For shit's sake, I see so many of my co-workers who are 'suppose' to be available during core hours, who, when they WFH, cannot be reached by inner-office instant message, e-mail or phone, don't call into the meetings they are suppose to. I repeat, you do not want to be one of those people. It makes you look bad and it will catch up with you sooner than you think.
...
In addition, I usually go to a cafe' or Library to work for half the day on Tuesday and Friday. Everyone knows it. When I'm there, I'm a lot less likely to video in. But I am ALWAYS available via email, jabber, etc.
Where I live we were fortunate enough to get UTOPIA up and running. It has forced the major cable internet providers to lower rates since they can't compete with the speed of fiber.
Telecommuting (in my experience) works very well when everyone knows when everyone else is working. I put in standard 8-5 hours. If someone wants to get ahold of me, they do (except a smaller than 1 hour lunch window that starts somewhere from 12-1). I am more predictably available than most folks in an office are at their desk.
An awful lot depends on the person (as you would expect). But predictability is key.
Re:No, that's what you get for using a dying langu
on
GitHub Hacked
·
· Score: 3, Insightful
While it's true that it was sloppy coding, it is also true that the default is not really safe - and it probably should be.
You're kidding, right? Any mail provider... I don't know what to say. * I hosted my own until a few years ago * yahoo * hotmail * my isp * everyone and their brother
I mean we know they are going to close them eventually as well, right?
I don't get it. Why are you just spreading FUD? OK, maybe you don't like google. But you can't come up with a single service that they have shut down and really inconvenienced their users. And you're naming gmail just looks dumb - they make money off that. And while it would not surprise me even a little if reader goes away, I fully expect that it will just roll into some other service they provide (plus, probably); not to mention that they make it trivial to migrate away, should you so choose: http://googlesystem.blogspot.com/2008/07/export-feeds-from-google-reader-folder.html
Usually there really isn't any good warning ahead in time.
... when it isn't google.
With Google it's just a few months.
Riiiight...
Not all of Google's services are free either, and since they most often don't release the source code, you are basically locked to their services.
OK - name one of google's services that they have canceled in a way that screwed the users. Where they lost their data or could not get it out in a very meaningful way.
Ethics, also known as moral philosophy, is a branch of philosophy that addresses questions about morality—that is, concepts such as good and evil, right and wrong, virtue and vice, justice and crime, etc.
Nearly by definition, what you eat (no matter what) is a subject of ethical debate - exactly *because* you don't think there is anything wrong with eating any kind of animal and because other people do.
You have to try hard not to see good examples out there in use. The most common case is the prototype version of the Decorator pattern, seen in the uniformization of DOM support across browsers done by jQuery (and similar libraries). Decorator patterns with multiple-class subclassing gets ugly fast, and is trivial with JS.
I *really* do enjoy ruby. If you have an opportunity to take it for a spin, I think you might enjoy it.
I seriously cut my teeth on Obj-C, but it's been quite a while. I remember it had reasonable decorator possibilities at the class and object level, but it was fragile base class where variables were concerned. Methods you could do anything with. I *think* that's changed in the past 10-15 years.
I never tried Smalltalk, but I thought it would decorate just as easily as javascript.
So I'm still hoping for something with strong subclassing support. I just enjoy 'em more.
I've tried the grandaddies of all of them - from Simula to Smalltalk to C++ to rolling my own object systems with procedural pointers... hell, I've even used CLOS. Objective C and Ruby aren't that much different (object-model-wise) from Smalltalk.
Prototype-base inheritance is a different animal from class-based. It is more flexible, can handle certain situations that cannot be handled elegantly in class-based inheritance (even with multiple inheritance and/or aspects). If you truly don't understand the advantages then either (a) you hate Javascript (not an uneasy thing to do) and it's colored your whole view of prototypical object systems or (b) you haven't used class-based OO enough to understand their limitations.
Since I'm coming up on 20 years of OO, maybe I can propose: (c) I really do like OO Languages and I really don't like prototypers.
It may be that Ada spoiled me for prototype languages very early on. And while Obj-C is a whole lot like smalltalk (though I never did the latter), ruby is a pretty amazingly flexible animal. I sure enjoy the hell out of it. Actually, I understand that recent Obj-C has added some of the feature I enjoy in Ruby.
It's rare to have an intelligent conversation on/. I'm curious
It is more flexible, can handle certain situations that cannot be handled elegantly in class-based inheritance
Prototype-based inheritance is much much more powerful than any kind of subclassing I've seen on any class-based OO language.
Have you tried ruby? Or even Objective-C?
The only ah-ha moment I've had with JS is more like "uh-huh. So it's going to take a lot more work to do the things I like to do with a language with strong support for subclassing."
From TFA: "Spontaneous choice to lie more or less can be influenced by brain stimulation," researchers Karton and Bachmann wrote in Behavioural Brain Research.
That's it. Based on a single study of 16 people in one test.
* Business - for the obvious reasons. It goes well with everything. * Sociology - it turns out that people are important in most jobs. You work with them, for them (boss), and for them (customers - whether asking how they would like that or figuring out what they would like. Oh, and the mix of people in that major may present a more interesting mix than in any engineering * Psych - because that also goes well with everything.
Slashdot Mirror
You mention being comfortable in java, but you also say (essentially) that you don't know a thing about client side coding. You mention WebObjects, which is rare, and I imagine most folks don't have a clue what that is. But you don't mention MVC, which seems odd to me.
You're going to write a new app using 2-4 new frameworks. As far as I'm concerned, frameworks are more work to learn than a new language.
As someone who enjoyed WO in the Obj-C days and suffered through it in the Java days, here's my advice:
Go with Ruby on Rails. Ruby is a fun language. Rails is a reasonable framework. On the client you could do a lot worse than jQuery, twitter bootstrap, and maybe Ember.js or backbone for the fancy stuff. I think that starting out with ember/backbone will give you a leg up when you make the move to non-web mobile platforms. Oh, and I do recommend coffeescript - it feels a lot saner to an OO developer than raw javascript.
In other words, Prop 13 protects millionaires.
I forgot, why do we need to protect millionaires? Why can't they take their windfall profits and move into less expensive accommodations?
You're a bit flamey, but I'll bite.
I believe that a home is not the same as a house. You should not be forced to move out of your home just because the houses in your neighborhood got bought up by rich folks.
I don't believe you're $ rich because your home is worth a lot. I don't think of a home as a liquid asset.
I do believe in a strong inheritance tax. So I guess I believe in protecting people's homes until they die. And I think that's going to be hard on the kids who grew up in the house if they can't afford the taxes, but that's where *I* would draw the line...
... But the law is so badly written that it has allowed some corporations (which don't have to worry about dying) to use shell games to conceal their continued ownership of a property even after they sell it, allowing them to reap the profits while keeping property taxes low for the new buyer. (How do you track down the ownership of a property when it's owned by some kind of huge conglomerate or partnership?) ... We seem to be stuck with it.
Ownership is easy. It's the name on the deed. The owner should not be protected from raising taxes on commercial property. It really doesn't matter where the shells are - as long as the owner gets taxed. They'll pass the costs up and down as they can.
As for being stuck with it - yup.
Prop 13 is why people who bought their homes when they were $75K (or less) can still afford to live in them now that they're worth $1M+(or much more) and they're living on retirement. I'm a big fan of rolling back prop 13 protection for businesses, which I think SHOULD need to keep up economically with their neighbors.
But toward the partent poster's point that we elect these folks to govern and not just tally their constituent's opinions, I sure agree.
Really? 99%?
Could you cite that?
Thanks.
This.
...
1) Be available when you're suppose to: For shit's sake, I see so many of my co-workers who are 'suppose' to be available during core hours, who, when they WFH, cannot be reached by inner-office instant message, e-mail or phone, don't call into the meetings they are suppose to. I repeat, you do not want to be one of those people. It makes you look bad and it will catch up with you sooner than you think.
...
In addition, I usually go to a cafe' or Library to work for half the day on Tuesday and Friday. Everyone knows it. When I'm there, I'm a lot less likely to video in. But I am ALWAYS available via email, jabber, etc.
If I don't do that I tend to get cabin fever.
Where I live we were fortunate enough to get UTOPIA up and running. It has forced the major cable internet providers to lower rates since they can't compete with the speed of fiber.
A what? Links, please.
Telecommuting (in my experience) works very well when everyone knows when everyone else is working. I put in standard 8-5 hours. If someone wants to get ahold of me, they do (except a smaller than 1 hour lunch window that starts somewhere from 12-1). I am more predictably available than most folks in an office are at their desk.
An awful lot depends on the person (as you would expect). But predictability is key.
While it's true that it was sloppy coding, it is also true that the default is not really safe - and it probably should be.
Google maps has been better than any local transit maps I've used - not that I've used all that many. (San Luis Obispo, CA)
I'm curious whereabouts you are that your local info is easier to get online.
Reader
... any news aggregator?
http://www.newsonfeeds.com/faq/aggregators
Gmail?
You're kidding, right? Any mail provider... I don't know what to say.
* I hosted my own until a few years ago
* yahoo
* hotmail
* my isp
* everyone and their brother
I mean we know they are going to close them eventually as well, right?
I don't get it. Why are you just spreading FUD? OK, maybe you don't like google. But you can't come up with a single service that they have shut down and really inconvenienced their users. And you're naming gmail just looks dumb - they make money off that. And while it would not surprise me even a little if reader goes away, I fully expect that it will just roll into some other service they provide (plus, probably); not to mention that they make it trivial to migrate away, should you so choose:
http://googlesystem.blogspot.com/2008/07/export-feeds-from-google-reader-folder.html
What's the deal?
Usually there really isn't any good warning ahead in time.
... when it isn't google.
With Google it's just a few months.
Riiiight...
Not all of Google's services are free either, and since they most often don't release the source code, you are basically locked to their services.
OK - name one of google's services that they have canceled in a way that screwed the users. Where they lost their data or could not get it out in a very meaningful way.
Yeah, it's a shame that you're 100% locked in to their free service, there is no warning, and you can't get your data out, or use any alternatives.
Oh, wait...
I realized, belatedly, that it is still in the title. Used to be prominent in the page - as I recall.
I was going to ask:
How is this "News for nerds - stuff that matters?"
But it looks like /. dropped that tagline. And a good thing, too, since this is just crap.
How?
Link please.
What panels did you buy, when, for how much, and who installed?
Just because PETA says something is unethical doesn't mean it is.
http://en.wikipedia.org/wiki/Ethics
Ethics, also known as moral philosophy, is a branch of philosophy that addresses questions about morality—that is, concepts such as good and evil, right and wrong, virtue and vice, justice and crime, etc.
Nearly by definition, what you eat (no matter what) is a subject of ethical debate - exactly *because* you don't think there is anything wrong with eating any kind of animal and because other people do.
Hmm. I can use Reader from my app account, but still can't use plus, there. I wonder if that's gonna change.
You have to try hard not to see good examples out there in use. The most common case is the prototype version of the Decorator pattern, seen in the uniformization of DOM support across browsers done by jQuery (and similar libraries). Decorator patterns with multiple-class subclassing gets ugly fast, and is trivial with JS.
I'm spoiled by the languages I've used. Ruby has very strong support for decoration at both the object and class level.
http://tenderlovemaking.com/2008/12/04/nokogiris-slop-feature/
I *really* do enjoy ruby. If you have an opportunity to take it for a spin, I think you might enjoy it.
I seriously cut my teeth on Obj-C, but it's been quite a while. I remember it had reasonable decorator possibilities at the class and object level, but it was fragile base class where variables were concerned. Methods you could do anything with. I *think* that's changed in the past 10-15 years.
I never tried Smalltalk, but I thought it would decorate just as easily as javascript.
So I'm still hoping for something with strong subclassing support. I just enjoy 'em more.
I've tried the grandaddies of all of them - from Simula to Smalltalk to C++ to rolling my own object systems with procedural pointers... hell, I've even used CLOS. Objective C and Ruby aren't that much different (object-model-wise) from Smalltalk.
Prototype-base inheritance is a different animal from class-based. It is more flexible, can handle certain situations that cannot be handled elegantly in class-based inheritance (even with multiple inheritance and/or aspects). If you truly don't understand the advantages then either (a) you hate Javascript (not an uneasy thing to do) and it's colored your whole view of prototypical object systems or (b) you haven't used class-based OO enough to understand their limitations.
Since I'm coming up on 20 years of OO, maybe I can propose:
(c) I really do like OO Languages and I really don't like prototypers.
It may be that Ada spoiled me for prototype languages very early on. And while Obj-C is a whole lot like smalltalk (though I never did the latter), ruby is a pretty amazingly flexible animal. I sure enjoy the hell out of it. Actually, I understand that recent Obj-C has added some of the feature I enjoy in Ruby.
It's rare to have an intelligent conversation on /. I'm curious
It is more flexible, can handle certain situations that cannot be handled elegantly in class-based inheritance
like what?
kurt@CircleW.org
Prototype-based inheritance is much much more powerful than any kind of subclassing I've seen on any class-based OO language.
Have you tried ruby? Or even Objective-C?
The only ah-ha moment I've had with JS is more like "uh-huh. So it's going to take a lot more work to do the things I like to do with a language with strong support for subclassing."
Maybe it's just that I like using the word super!
From TFA:
"Spontaneous choice to lie more or less can be influenced by brain stimulation," researchers Karton and Bachmann wrote in Behavioural Brain Research.
That's it. Based on a single study of 16 people in one test.
This isn't news. It hardly qualifies as gossip.
I'll take a language that has strong support for subclassing, thanks.
People are doing some cool stuff with javascript - but I think it's in spite of the language, not because of it.
(claimer: I have to deal with JS every day)
* Business - for the obvious reasons. It goes well with everything.
* Sociology - it turns out that people are important in most jobs. You work with them, for them (boss), and for them (customers - whether asking how they would like that or figuring out what they would like. Oh, and the mix of people in that major may present a more interesting mix than in any engineering
* Psych - because that also goes well with everything.