Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build tooling to make it possible to add caveats (e.g. Redis works differently on Windows) or OS-specific hints and links #48

Closed
nicorafales opened this issue Sep 19, 2019 · 7 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@nicorafales
Copy link

nicorafales commented Sep 19, 2019

Hi!
I want to propose to change the focus of development based on macOS as a de facto platform. Most future developers out there may not have access to a macbook or similar hardware so all the docs should include Windows and GNU/Linux links for tooling instalation and configuration on par with the huge amount of links we can find all over the place for macOS users.
I have been a Laravel (& Symfony) developer for the past 3 years (working on home projects with Windows 10 and at companies using GNU/Linux) and i've yet to try a mac. I don't need it, i don't want it and i don't hate it

@mattstauffer
Copy link
Member

That's an opportunity for you to contribute to Onramp! I use a Mac; as does Taylor. We know a lot about what works well on Macs. We don't know as much about what works well in other settings.

So, we have to rely on people who use those platforms to contribute. It doesn't have to be a "change the focus", it should just be "if you use other tools, contribute".

I would recommend specific suggestions. For example, is this not enough? Is there anything else on Onramp that's actually Mac-specific right now?

image

I will make one caveat: This site will always primarily embody a "happy path". it's not about giving a million options. It's about giving one preferred option. So I'm not going to recommend seven different local dev environments; but I'm fine to recommend a single one per environment.

@nicorafales
Copy link
Author

nicorafales commented Sep 21, 2019

For now, it's only the local environment. But probably when docs get bigger, everything outside of the bounds of Laravel has to have a link to the other OSes. For example, the driver for Redis doesn't work the same way, has less features, in Windows. So subscribing Queue jobs or Horizon doesn't work out of the box without tweaking. Deployments section should be diferent for all three main OSes (not counting I/P/SaaS platforms).
Yeah! we all have to help to contribute to the docs since we work with those configurations. I just wanted to make it visibile so it's a present matter from now on for docs and trainings.

I already did (i'm Nicolás)

@mattstauffer
Copy link
Member

Hey Nicolás! You sure did--thanks so much for your patch!

I think there's going to have to be a balance. I do agree that I want us to consider all development stacks. But I also want to focus on "how it works, at its simplest" and have everything else be caveats--links to "if you have this problem here's a solution", rather than having to run everyone through it.

I think it's good for us to consider building in a concept into the platform itself about "adding caveats" or "adding a concept of which OS someone is in" so we can help round the thing out without making it too clumsy. 👍🏻 Thanks for bringing it up!

@mattstauffer
Copy link
Member

I'm going to re-name the issue so it tracks more of how I'm thinking about it now.

@mattstauffer mattstauffer changed the title Move the focus away from macOS as the first development platform Build tooling to make it possible to add caveats (e.g. Redis works differently on Windows) or OS-specific hints and links Sep 24, 2019
@mattstauffer mattstauffer added enhancement New feature or request help wanted Extra attention is needed labels Oct 24, 2019
@jonsugar
Copy link
Contributor

jonsugar commented Oct 24, 2019

What if (like the language preference) the user can specifiy their prefered OS/Environment details Onramp can then tailor their experience.

Maybe upon signup there is a wizard type widget that lets the user specifiy:

  1. Their language.
  2. Their appropriate track–"Brand-new developer", "Front-end developer" or "Wordpress developer".
  3. What environment they are learning on-Linux, Mac or Windows.

Of course the user will be able to change the preferences but I think that would be a good user experience.

Caveat here is that we would need a lot of content because we would need variants of all combinations where appropriate but as a goal I think its reasonable.

@jonsugar
Copy link
Contributor

jonsugar commented Oct 24, 2019

That's an opportunity for you to contribute to Onramp! I use a Mac; as does Taylor. We know a lot about what works well on Macs. We don't know as much about what works well in other settings.

So, we have to rely on people who use those platforms to contribute. It doesn't have to be a "change the focus", it should just be "if you use other tools, contribute".

I would recommend specific suggestions. For example, is this not enough? Is there anything else on Onramp that's actually Mac-specific right now?

@mattstauffer FYI I might be a weirdo but I have set-up development environments on both my Mac and Windows 10 machines. I will literally wake up one day and feel like switching platforms and will stick with that environment for a while before switching again.

If you like, I will be happy to work on the "one reccomended windows environment".

@jonsugar
Copy link
Contributor

@mattstauffer I think this can be closed due to #24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants