Hi JavaPosse,
Today, the name of JavaPosse in my list of podcast subscribtions in
iTunes has suddenly changed to "Pipes Output".
What's happening? You're not renaming the podcast to "Pipes Output",
are you? ;-)
regards
Jesper de Jong
--~--~-~--~~~---~--~~
You re
well one could argue that, though im not sure if native threads have
such guarantee - in which case, java may only be delegating to native
that said, you can try disabling biased locking (starting from java 6
i think) and see if it makes any difference
On Tue, Nov 3, 2009 at 5:40 PM, Brent Ryan
Yes, I was indeed saying that java didn't break anything. your app was
broken from the start by relying on something that isn't in the spec.
Every release of the JVM *breaks* lots of things you shouldn't have
relied upon, every time it updates, especially around the topic of
threading.
double-ch
> I'd start with BlueJ, if you're new to programming in general and Java
> specifically (bluej.org).
>
> Wayne
+1
BlueJ takes a different tack to learning Java, giving object oriented
fundamentals a greater billing than syntax and other details like running
Java apps from the command line. It
Aha - one of my Alumni (but a few years before I was there).
I believe that the for comprehension approach will gradually pick up
features until it becomes something like LINQ although maybe without
the SQLish syntax (which is a matter of taste anyway, I don't
particularly like or dislike SQL so
Dick,
Thanks for dropping in. And I thought you loved the groovy!
> does tend to conveniently ignore some features in Scala that really do
> push Scala ahead in those areas. One such example is traits. Unless I
Granted. Thats the problem with translating C# to Scala. Going the
other way I might
On Tue, Nov 3, 2009 at 7:11 PM, kirk wrote:
>
>
>
> Marcelo Fukushima wrote:
>> i should probably write in a better way (i guess i cant write in
>> english as well as i can read)
>>
>> what i meant was that os thread could potentially behave like how java
>> threads behave: there are not guarant
I didn't even get a chance to reply but can I be in the scope of the
idiot block too?
On Nov 3, 7:47 pm, Steven Herod wrote:
> Are you sure you needed to refer to the respondents as 'idiots'?
>
> Had a bad day?
>
> On Nov 3, 5:45 pm, Reinier Zwitserloot wrote:
>
>
>
> > You write an _obvious_ t
Marcelo Fukushima wrote:
> i should probably write in a better way (i guess i cant write in
> english as well as i can read)
>
> what i meant was that os thread could potentially behave like how java
> threads behave: there are not guarantees that any given thread will be
> given its timeslice i
Bayan,
I agree with Brian. It's best to start off with your favorite text editor
and command line compiling, etc. when learning the language. It will help
you focus on the language and not the IDE.
Eclipse is probably the industry defacto standard (at least owns majority
popularity share) Java
I think that make a simple system is the best way.
You must chose in two of the most popular ways, web develop, and win develop
(is totally different) .
Then, take an hello world example, and start coding.
Lucky
Matias Berrueta
On Tue, Nov 3, 2009 at 3:17 PM, Brian Ehmann wrote:
>
> While
No Problem!
On Nov 3, 8:19 am, Carl wrote:
> Thank you Brian.
>
> On Nov 1, 11:29 pm, Brian wrote:
>
> > On Nov 1, 6:21 am, Carl wrote:
>
> > > Brian,
>
> > > Since you have the standard one working (except for the issue about
> > > jar signing you mentioned), would you mind posting a complete
> I start learning Java in this month by reading Thinking in Jave book,
> before this time i learn bit about C++ and C#, but I don't know what
> best IDE i can use it?
I'd start with BlueJ, if you're new to programming in general and Java
specifically (bluej.org).
Wayne
--~--~-~--~~
Hello everyone,
I start learning Java in this month by reading Thinking in Jave book,
before this time i learn bit about C++ and C#, but I don't know what
best IDE i can use it?
please, give me your advices for learning Java for go on it very good,
becuase I .plan to complete my study in this lang
Then maybe the spec is where the flaw is...
Sent from my iPhone
On Nov 3, 2009, at 10:45 AM, Marcelo Fukushima
wrote:
>
> i guess what reinier was trying to say was that your code (as far as
> vm spec goes) was broken from the start and (again, from the vm spec
> perspective) lucky timing an
i guess what reinier was trying to say was that your code (as far as
vm spec goes) was broken from the start and (again, from the vm spec
perspective) lucky timing and scheduling just made it work correctly
On Tue, Nov 3, 2009 at 3:26 PM, Brent wrote:
>
> I just don't think that it's a good idea
While learning language fundamentals, I would recommend you use your
favorite text editor until you feel you are ready to write more
complex applications like web apps. This way you will learn the
language instead of the IDE. Plus it will help you become familiar
with using the javadocs instead
i should probably write in a better way (i guess i cant write in
english as well as i can read)
what i meant was that os thread could potentially behave like how java
threads behave: there are not guarantees that any given thread will be
given its timeslice in the CPU. In that regard, the jvm spe
Marcelo Fukushima wrote:
> well one could argue that, though im not sure if native threads have
> such guarantee - in which case, java may only be delegating to native
>
> that said, you can try disabling biased locking (starting from java 6
> i think) and see if it makes any difference
>
I may
I just don't think that it's a good idea to say...Let's break
something so that we can optimize the JVM for most cases without
providing an option that allows the JVM to execute threads one way vs.
another. This used to work in JDK 1.4.
Does anyone know how .NET solves this problem with the CLR?
This is an interesting discussion nucleus for sure, but the article
does tend to conveniently ignore some features in Scala that really do
push Scala ahead in those areas. One such example is traits. Unless I
have missed something, C# still doesn't have traits or mixins and
relies on the interface
Thank you Brian.
On Nov 1, 11:29 pm, Brian wrote:
> On Nov 1, 6:21 am, Carl wrote:
>
> > Brian,
>
> > Since you have the standard one working (except for the issue about
> > jar signing you mentioned), would you mind posting a complete working
> > example?
>
> Here's my working pom.xml:
> [..
Casper Bang wrote:
>> Well, I have co-workers wearing glasses and frankly nobody has ever
>> complained about Swing :-)
>>
>
> You misunderstand. Try booting up windows in a VM, and then inspect
>
Oops. thanks for pointing out my misunderstanding; I thought you was
referring to the font re
> Well, I have co-workers wearing glasses and frankly nobody has ever
> complained about Swing :-)
You misunderstand. Try booting up windows in a VM, and then inspect
the widget hierachy of a Swing app using Spy++ or similar. You will
notice there's no way to introspect and extract any informatio
Casper Bang wrote:
> AFAIK that's entirely up to the native peer, how it chooses to render
> - there shouldn't be anything preventing SWT from taking advantage
> of the GPU. Then again, this topic is more interesting in Swing since
> the whole UI effectively has to be emulated whereas SWT is us
AFAIK that's entirely up to the native peer, how it chooses to render
- there shouldn't be anything preventing SWT from taking advantage of
the GPU. Then again, this topic is more interesting in Swing since the
whole UI effectively has to be emulated whereas SWT is using native
stuff which is alre
Christian Catchpole wrote:
> You can embed OpenGL panels from LWJGL or JOGL... I've done this.
> Works nice. You can even embed Swing panels if you want.
>
> http://www.eclipse.org/swt/opengl/
>
It's not what I'm talking of. You're referring to a direct use of OpenGL
for 3D stuff and of cour
Are you sure you needed to refer to the respondents as 'idiots'?
Had a bad day?
On Nov 3, 5:45 pm, Reinier Zwitserloot wrote:
> You write an _obvious_ trolling post, with a link to your own blog no
> less, and yet you got 3 idiots to stop into your steaming pile?
>
> Wow. I'm impressed.
>
> NB:
Reiner, thank you for your comments,
There were some good comments on the blog so my (light) baiting
worked.
I know the title was provocative, yes. But "almost" leaves room for
hope that Scala can be "better" than C# if some of the usabilty gaps
are filled in. And those gaps could be filled in,
29 matches
Mail list logo