pointless complaining :)

STOP SHOWING ME VIDEOS OF WONDERFUL THINGS I CAN”T DO YET! Or release the pre-release versions! yes yes yes :slight_smile: I know :slight_smile: and I’ll go and make myself a cocktail now and keep waiting but seriously :wink: keep it a secret until I can have it! or give it to me to play with!

how about a wip night build :stuck_out_tongue:

it usually happens on tuesdays :wink:

Actually to me it is far from pointless. It gives a more realistic expectation of what features are/are not coming in the first releases of each thing shown (e.g. Web 2.0, Workers, Android). Based on the Xojo public roadmap when can make a SWAG (but pretty safe bet) that some of the demos won’t make it to 2020R1 features. We don’t even know yet if more than the first roadmap priority will be in R1.

I’m guessing those of us with Pro accounts – and therefore Beta access – will know “soon” (whatever that means) for R1. With many of us having more down time right now do to travel / work restrictions, it admittedly would be fun to have that available now. But I’d much rather they release betas with more things working, then put out something prematurely just to satisfy some pre-conceived target date.

Workers arent in R1 (although that wasnt clear to me from geoffs initial presentation)

Toward the end of the video he did say something like “coming later this year” when talking about multicore, which I took to mean the Workers class. So my SWAG is 2020R1 will have at least the first priority of the roadmap but how much of #2-4 will be included too is just a guess. My guess is not beyond #2 – if that – but would be happy to be proven wrong “soon”.

I think this is James joking complaint from the beginning of this thread

I think there are a lot of people anxious to quit waiting for the future to arrive :slight_smile:

Geoff told the Web 2 will be in r1 and PDFDocument, if I remember correctly.
You need to watch the Q&A, too.

Anyway, there is always a risk, something is too buggy to release and is moved to r2.

pdfdocument is not risky.
web 2 is risky, specially as the ide for web 2 will not compile web 1 anymore.

For me, I have the plain impression that the preview sparked great feedbacks that the engineers took notes and will need to think a bit about them. Some of those feedbacks were crucial for a really good start of the release of some of those products. Workers without shared memory are not very useful in substitution of threads, some feedbacks to Android team were also very helpful like setting the minimum API level of the final APK to avoid planned compatibility issues.

workers without shared memory are useful - not for a certain set of taks that have to move huge amounts of data but thats unlikely to be everyone’s need

workers that cant incorporate any code other than what is in jobrun arent as useful as they could be

personally I see that as a much bigger impediment

[quote=481319:@Norman Palardy]workers that cant incorporate any code other than what is in jobrun arent as useful as they could be

personally I see that as a much bigger impediment[/quote]

Totally agree; and I even use the MBS shared memory APIs in my current console helpers

Didn’t say that isn’t. I did say:

You mean that is some possibility of not calling a “global” lib that is found in the project? I can not even think that Xojo would conjecture anything like this.

[quote=481319:@Norman Palardy]workers without shared memory are useful - not for a certain set of taks that have to move huge amounts of data but thats unlikely to be everyone’s need

workers that cant incorporate any code other than what is in jobrun arent as useful as they could be

personally I see that as a much bigger impediment[/quote]

While I would like to see shared memory support, I agree…

Because of code management, If you really want to do many non trivial things, you will still need to use a separate console app for it to be practical…

BTW I wonder if this will be available with just a desktop license or if it would require pro… given the limitations one should not need either Pro or a console license for workers IMO.

For that matter IMO console should be part of desktop in this multicore world, but that is a different issue.

-Karen

Yes - thats what we have been told so far

https://forum.xojo.com/conversation/post/480928

[quote=480928:@Kem Tekinay]
Q&A just wrapped up. Just to be clear, in v.1 the Worker won’t have access to anything in the main project, including your classes, modules, or methods. That will have to be included in the ProcessJob (or whatever it was called) event.

At least, for now.[/quote]

EDIT : Oh and not in 2020r1 anyway

for the record, yes I was joking :slight_smile: yes I am frustrated to wait as I want it now, but thats just silly! You can’t have what they don’t release and my frustration is humorous and not meant to be taken as any real criticism! If I wasn’t totally excited to get my hands on the new stuff I wouldn’t be frustrated that I didn’t have it! Absolutely no negative perception was implied or insinuated! There will always be things they choose to do that will frustrate me :wink: As I am not in charge :wink: but these are not those things! I am just so ready to get down and working with the Web2.0 stuff I can’t even tell you :slight_smile: thus the jokes! And all the smilies in my post. If anyone read what I wrote above and believed I was actually angry or upset at anything please read again and in your mind insert a smily or winky face emoji in the place of every period!

I think a lot of people share your excitement for Web framework 2.0. If it helps with your frustration, the MVPs have been testing and using it and it’s wonderful :wink: Does that help?! But seriously, Geoff has confirmed that Web 2.0 will be in Xojo 2020R1, so hang in there.

It is pointless. Until Xojo ship these features (or even let us pre-release testers use them) they are vapourware.

Pointless complaining is pointless. Vaporware never reaches the release, usually they are exist due to hoax, marketing pressure to show a phony thing, or bankruptcy avoiding completion. MVPs are “playing” with it, so consider a better term, “preliminary preview” of features under development. Few of those will not reach the final product in early releases, and will not be exactly the same in the final version (and I hope that some gets even better due to feedbacks). And differently of few people, I like to see and emit some “anticipated” opinions.